Security audit

Django Production Engineering

Security checks for vulnerabilities and agentic risk

Overview

This Django guidance skill is mostly coherent, but it includes a production multi-tenant pattern that could break tenant isolation if copied.

Before installing or using this skill, treat its code snippets as templates that require engineering review. Do not copy the multi-tenant TenantMiddleware or TenantManager pattern as written; tenant access should be authorized through authenticated membership and fail closed. Pin build tools in Docker examples and require explicit review before applying generated deployment, authentication, CI/CD, or data-access changes.

A.I.G

Vulnerability Patterns

Insecure DependenciesIntroduces malicious components through unsafe dependency sources
Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review

Findings (2)

T09 · Insecure Skill Coding Practices

Error

Location: SKILL.md:1078
Finding: Broken Tenant Isolation in Recommended Multi-Tenant Pattern
Content: View full analysis
Remediation: View remediation

T08 · Insecure Dependencies

Warning

Location: SKILL.md:979
Finding: Unpinned Build Tool Creates Mutable Supply-Chain Input
Content: View full analysis
Remediation: View remediation
" ``` 2. Where supported, require a verified package hash: ```text uv== \ --hash=sha256: ``` 3. Install from a locked requirements file using `pip install --require-hashes`. 4. Use a controlled internal package mirror or an approved artifact repository. 5. Add dependency scanning and provenance verification to CI. 6. Update the pinned version through a reviewed dependency-update process rather than implicitly during every build. 7. Avoid exposing production secrets as Docker build arguments or environment variables during dependency installation. ]]>

SkillSpector

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The quick-start section uses very broad natural-language trigger phrases such as "Review this Django project" and "Production checklist," which can easily overlap with ordinary user requests in unrelated contexts. In agent platforms that auto-route or auto-activate skills based on prompt similarity, this increases the chance of unintended invocation, causing the skill to steer outputs, expose internal project context to the skill, or interfere with higher-priority instructions.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The skill exposes very broad natural-language triggers such as 'Review this Django project', 'Deploy this Django app', and 'Set up authentication' without defining clear activation boundaries, required confirmations, or exclusions. In an agent setting, this can cause overbroad execution or generation of sensitive operational guidance from loosely matched prompts, increasing the risk of unintended actions, unsafe changes, or misuse in higher-privilege contexts.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.