Feature/bun within range fixture#562
Merged
sonukapoor merged 13 commits intoJun 7, 2026
Merged
Conversation
Apply OSV-validated direct fixes, commit lockfile changes, and open a structured PR via gh. Supports --base and respects --fail-on threshold. Closes OWASP#367
… on applied fixes
Check file existence before git add so npm-only repos do not fail on missing yarn.lock, pnpm-lock.yaml, and other optional lockfiles.
Contributor
Author
|
@sonukapoor Please Review the PR When you have free time |
sonukapoor
approved these changes
Jun 7, 2026
sonukapoor
left a comment
sonukapoor
left a comment
Collaborator
There was a problem hiding this comment.
Tested on the branch — Bun path reconstruction is working correctly. bun update follow-redirects is generated for the within-range transitive fix and bun add axios@0.32.0 for the direct vulnerability. 416/416 tests pass. Nice work including the actual parser improvement alongside the fixture.
One minor note: the PR title should follow our naming convention — feat: add bun-within-range lockfile fixture. Not blocking.
Collaborator
|
Merged — thank you @coder-Yash886! |
Merged
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
2 participants
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.
(fixture #7 ) bun-within-range
Summary
Adds the
bun-within-rangecrafted fixture for issue #540 — a minimal Bun lockfile where a transitive vulnerability (follow-redirects@1.14.0) can be fixed within the parent's declared range (axios@0.21.1allows^1.10.0), so the scanner emitsbun update follow-redirectsinstead of a parent upgrade.Also enhances the
bun.lockparser to reconstruct transitive dependency paths from package relationships (required for within-range remediation on Bun lockfiles).What was added
examples/bun-within-range/package.jsonaxios@0.21.1examples/bun-within-range/bun.lockfollow-redirects@1.14.0underaxiossrc/parsers/bun-lock.tsbun.lockpackage graphsrc/parsers/index.tstests/parsers.test.tsproject → axios → follow-redirectspath reconstructionexamples/readme.mdScan output
npm install && npm run build node dist/index.js examples/bun-within-range --verbose