Dependency installed from a git branch
MediumAV-DEP-004Supply chainCore packNew in 2.0
What it finds
A package is installed from a git repository branch (or default branch) instead of a release or a full commit hash.
Why it matters
Whoever can push to that branch decides what code you install next time — no version, no review.
What an attacker could do: Upstream pushes change your agent's code silently.
How to fix it
Use a published release, or pin to a full 40-character commit hash.
Pro shows the corrected code for your exact file, step by step, and re-scans to confirm the fix. See plans
Check details
- Finding code
- DEPENDENCY_FROM_GIT_BRANCH
- How it detects
- Looks for a specific risky pattern in the code or config.
- Confidence
- Definite: the risky setting is written plainly in the file.
- Scans
- Any text-based agent source or configuration (JS/TS/Python/JSON/YAML)
- OWASP LLM Top 10
- LLM05 - Supply Chain Vulnerabilities
- NIST AI RMF
- GV-6.1
- SOC 2
- CC8.1
Check your agent for this
Paste your agent code or MCP config. The free scan runs all 124 checks in about 10 seconds — no account needed.