django-security-hunter 0.1.0

Django + DRF security, reliability and performance inspector

django_security_hunter

Django + DRF Security, Reliability, and Performance Inspector.

django_security_hunter helps backend teams catch risky patterns early: security misconfigurations, authorization gaps, abuse-protection weaknesses, API correctness issues, and performance/reliability smells.

Why django_security_hunter

AI-assisted coding improves speed, but it can also introduce hidden backend risks.
django_security_hunter gives fast, actionable feedback during development and in CI before code reaches production.

Features

• Static and configuration scanning for Django + DRF projects
• Runtime profiling mode scaffold for query explosion / N+1 detection
• Output formats: console, json, sarif
• CI-friendly exit codes by severity threshold
• GitHub Security integration through SARIF

Documentation

• Rule Catalog
• Architecture Overview

Installation

From PyPI:

pip install django-security-hunter

Python package / CLI: django_security_hunter.

From source (clone into a folder name that matches the project):

git clone https://github.com/abu-rayhan-alif/djangoGuard.git django-security-hunter
cd django-security-hunter
python -m venv .venv
# Windows PowerShell
.venv\Scripts\Activate.ps1
pip install -e .[dev]

Quick Start

django_security_hunter scan --project . --format console
django_security_hunter scan --project . --format json --output reports/django_security_hunter.json
django_security_hunter scan --project . --format sarif --output reports/django_security_hunter.sarif

Commands

django_security_hunter scan

Runs static/config analysis and emits a report.

django_security_hunter profile

Runs runtime-oriented profiling checks (currently scaffolded in v0.1).

django_security_hunter init

Creates a default django_security_hunter.toml file in the target project.

CLI Options

• --project Project root path
• --settings Django settings module (example: config.settings)
• --format console | json | sarif
• --output Output file path
• --threshold INFO | WARN | HIGH | CRITICAL

Configuration

Configuration is loaded in this order:

1. django_security_hunter.toml (project override)
2. pyproject.toml -> [tool.django_security_hunter]

Example:

severity_threshold = "WARN"
query_count_threshold = 50
db_time_ms_threshold = 200

Rule Catalog (V1 Target)

Rule ID	Severity	Description
DJG001	CRITICAL	DEBUG=True in production
DJG002	HIGH	Suspicious/hardcoded SECRET_KEY
DJG020	HIGH	DRF default permissions missing or AllowAny
DJG040	WARN/HIGH	Query count per test above threshold
DJG041	HIGH	Repeated query signature indicates N+1
DJG070	HIGH	Risky XSS usage patterns detected

Full rules and implementation progress can be maintained in docs/rules.md.

Output Formats

Console

Human-readable output for local development.

JSON

Stable schema for automation and custom dashboards.

SARIF

SARIF v2.1.0 output for GitHub PR annotations and Security tab integration.

Exit Codes

• 0: No findings at or above threshold
• 2: One or more findings at or above threshold

GitHub Actions Integration

Workflow file: .github/workflows/ci.yml

On every push and pull request:

• installs dependencies
• runs tests
• generates SARIF report
• uploads SARIF to GitHub Security

Docker

Build and run:

docker build -t django_security_hunter:local .
docker run --rm django_security_hunter:local django_security_hunter scan --project /app --format console

Using Docker Compose:

docker compose run --rm django_security_hunter django_security_hunter scan --project /app --format console

Limitations

• Some future rules are heuristic and may produce false positives
• Runtime profiling depends on project test coverage quality
• Rule precision improves with project-specific tuning and allowlists

Roadmap

• Django settings hardening rules (DJG001-DJG012)
• DRF auth/permission/throttle checks (DJG020+)
• Static code pattern rules (XSS/SSRF/deserialization/secrets)
• Concurrency and atomicity heuristics (DJG050+)
• Runtime N+1 and DB-time evidence improvements (DJG040+)
• Optional dependency vulnerability integrations

Contributing

Contributions are welcome.

Please follow these guidelines:

1. Open an issue for major changes
2. Add tests for every new rule
3. Keep rule IDs stable and documented
4. Include remediation hints with findings

License

MIT