deps/locked-install
Installs use the lockfile strictly
A capability: each stack checks it with its own tools, and every implementation that runs must pass. Implemented for dotnet, flutter, go, hugo, java, kotlin, node, php, python, ruby, rust.
| Severity | warning |
| Tiers | 1, 2 |
| Stacks | any |
| Scope | each |
| Kind | capability |
| Source | library v0.8.0 |
| Selected by | fleetlint-recommended@v0.8.0 |
Requirement
A task-runner recipe or a CI step installs (or verifies) dependencies in the package manager’s locked mode, which fails when the lockfile and the manifest disagree instead of resolving new versions, and no recipe or CI step installs in a mode that rewrites the lockfile. Recipes of targets named for updating (update, upgrade, lock, bump) are exempt; comments and echo lines do not count. For a workspace member the repository’s CI counts, and a parent directory’s Makefile, justfile or Taskfile counts for the locked install.
Why
An install that quietly re-resolves builds and tests something other than what the lockfile in git says, and the drift shows up only in production.
Fix
Use the locked install in CI and in the check targets (npm ci, uv sync –locked, cargo –locked, …).
Agent instruction: Switch the CI and task-runner installs to the package manager’s locked mode; if that fails, regenerate the lockfile in a separate commit rather than relaxing the install.
Sources
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, Pinned-Dependencies)
- https://fleetlint.org/baseline/#dependencies (convention)
Generated by fleetlint docs from catalog v0.8.0.