security: enforce frozen lockfile in Docker builds#1011
Open
security: enforce frozen lockfile in Docker builds#1011
Conversation
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Hardens Docker builds against npm supply chain attacks by enforcing lockfile-pinned installs.
Changes:
Why: During the axios supply chain attack (2026-03-31), was briefly live on npm. Bare / ERR_PNPM_NO_PKG_MANIFEST No package.json found in /Users/ibrobaba/CodeStuff/Cohere/secops without can silently resolve to a newer version than what's in the lockfile if someone runs with or if the lockfile is absent from the build context. / makes the build fail if the lockfile is missing or inconsistent.
Related: Cohere internal report: axios-supply-chain-attack-2026-03-31