deps/locked-install/rust
Installs use the lockfile strictly
Implements deps/locked-install for rust.
| Severity | warning |
| Tiers | 1, 2 |
| Stacks | rust |
| Scope | each |
| Kind | expr |
| Source | library v0.8.0 |
| Selected by | fleetlint-recommended@v0.8.0 |
Requirement
A recipe or CI step runs cargo with --locked (or --frozen), so a Cargo.lock that no longer matches Cargo.toml fails the build instead of being rewritten.
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.
Check
(taskrunner.recipes.filter(t, !t.matches(r'(?i)update|upgrade|lock|bump|renovate')).map(t, taskrunner.recipes[t]).flatten()
+ params.runners.filter(f, file(f)).map(f, lines(f)).flatten()
+ workflows().map(w, steps(w).map(s, s.run.split("\n")).flatten()).flatten())
.filter(l, !l.matches(params.noise)).exists(l, l.matches(r'\bcargo\s[^;&|]*--(locked|frozen)\b'))Parameters
noise:^\s*[@+-]*\s*(\{\{[^}]*\}\}\s*|\$[({][A-Za-z_]+[)}]\s*)?(#|//|echo\b|printf\b)runners:[../Makefile ../justfile ../Justfile ../Taskfile.yml ../Taskfile.yaml ../../Makefile ../../justfile ../../Justfile ../../Taskfile.yml ../../Taskfile.yaml ../../../Makefile ../../../justfile ../../../Justfile ../../../Taskfile.yml ../../../Taskfile.yaml]
Fix
Add --locked to the cargo build/test commands in CI and the check targets.
Agent instruction (from deps/locked-install): 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)
- https://doc.rust-lang.org/cargo/commands/cargo-build.html (spec)
- https://fleetlint.org/stacks/#rust
Generated by fleetlint docs from catalog v0.8.0.