repo/lockfile-committed
Dependency lockfile is committed
A capability: each stack checks it with its own tools. Implemented for cpp, dotnet, flutter, go, hugo, java, kotlin, node, php, python, ruby, rust.
Combine: all. Every implementation that runs must pass: each stack in the repository meets the requirement with its own tools.
| Severity | error |
| Tiers | 1, 2 |
| Stacks | any |
| Scope | each |
| Kind | capability |
| Source | library v0.5.0 |
| Selected by | fleetlint-recommended@v0.5.0 |
Requirement
Each stack’s dependency manager has its lockfile tracked in git next to the manifest, or, for a member of a workspace that keeps one lockfile for all members (npm, pnpm, yarn and bun workspaces, Cargo, uv and pub workspaces), at the workspace root; a manifest without dependencies needs none.
Why
Builds are reproducible only when dependency versions are pinned in git.
Fix
Generate the lockfile with the package manager and commit it; remove it from .gitignore.
Agent instruction: Run the package manager to produce the lockfile, remove any .gitignore entry for it, and commit it.
Sources
- https://github.com/ossf/package-manager-best-practices/blob/main/published/npm.md (guidance)
- https://fleetlint.org/baseline/#dependencies (convention)
Generated by fleetlint docs from catalog v0.5.0.