AAK-SUPPLY-004: No lockfile present
- Severity
- MEDIUM
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/supply_chain.py- Auto-fixable
- No.
- SARIF name
NoLockfilePresent
What it detects
A package manifest exists but no lockfile was found. Without lockfiles, dependency versions float and can be silently updated.
How to fix
Generate the lockfile for the manifest named in the finding and commit it: npm install (package-lock.json), yarn, pnpm install or bun install, uv lock, poetry lock, pdm lock, pipenv lock or cargo generate-lockfile.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-SUPPLY-004
Limitations
Checks the project root only: a package.json needs a package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lock or bun.lockb, a pyproject.toml needs a poetry.lock, uv.lock, Pipfile.lock or pdm.lock, a Pipfile needs a Pipfile.lock and a Cargo.toml needs a Cargo.lock. A lockfile only has to exist, so an empty one passes, a Python project that declares its dependencies in requirements.txt alone is not checked, and neither is a manifest in a sub-directory.
References
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
- OWASP Agentic Top 10: ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-06 (Missing Lockfile)
- CSA AI Controls Matrix (AICM): STA-02
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-SUPPLY-004.md: the page then shows that text, with the registry reference appended under it.