django-seal

PyPI

Is django-seal safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for django-seal v1.7.1. Trust score: 90/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

django-seal Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

django-seal Capabilities & Permissions

What django-seal can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

/usr/ (r)

AGENTS.md for django-seal

Good instructions lead to good results. brin adds django-seal documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

django-seal Documentation & Source Code

For the full django-seal README, API documentation, and source code, visit the official package registry.

Frequently asked questions about django-seal safety

Weekly Downloads

13.0K

Version

1.7.1

Last Scanned

Feb 12, 2026

Trust Score

90/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is django-seal Safe? | PyPI Safety Scan - brin