chore(ci): add lockfile-lint PR check for yarn.lock injection prevention#7114
Open
jstirnaman wants to merge 1 commit intomasterfrom
Open
chore(ci): add lockfile-lint PR check for yarn.lock injection prevention#7114jstirnaman wants to merge 1 commit intomasterfrom
jstirnaman wants to merge 1 commit intomasterfrom
Conversation
Add a GitHub Actions workflow that validates yarn.lock on every PR, ensuring all resolved URLs use HTTPS and point to registry.yarnpkg.com. Prevents lockfile injection attacks where a PR modifies resolved URLs to fetch packages from attacker-controlled hosts. Uses lockfile-lint@5.0.0 via npx (no new dependencies in package.json). SHA-pinned actions, sparse checkout of yarn.lock only, least-privilege permissions.
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
1 participant
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
Add a GitHub Actions workflow that validates
yarn.lockon every PR, preventing lockfile injection attacks.What it does
Runs
lockfile-lint(v5.0.0, vianpx) to verify that everyresolvedURL inyarn.lock:http://,git://, or bare URLs)registry.yarnpkg.com(rejects unknown/attacker-controlled hosts)Why this matters
Lockfile injection is a supply-chain attack where a PR modifies
yarn.lockto redirect package resolution to attacker-controlled hosts. The change is easy to miss in code review because lockfiles are large and auto-generated. This check catches it automatically.Reference: Lockfile injection research (Liran Tal, 2019)
Workflow design
yarn.lockyarn.lock(not the full repo)actions/checkout@v6.0.2,actions/setup-node@v6.3.0permissions: contents: read,persist-credentials: falsenpx --yes lockfile-lint@5.0.0(not added topackage.json)Baseline verified
All 802
resolvedentries inyarn.lockcurrently point tohttps://registry.yarnpkg.com/— no false positives expected.Test plan
actionlintpasses on the new workflowlockfile-lintreports "No issues detected" on currentyarn.lockhttp://evil.example.com) correctly detected and exits non-zero