Skip to content

Add deep-chain-no-fix regression fixture (#528)#558

Merged
sonukapoor merged 1 commit into
OWASP:mainfrom
Ayush7614:ayush19
Jun 7, 2026
Merged

Add deep-chain-no-fix regression fixture (#528)#558
sonukapoor merged 1 commit into
OWASP:mainfrom
Ayush7614:ayush19

Conversation

@Ayush7614

@Ayush7614 Ayush7614 commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds examples/deep-chain-no-fix/ for Discussion Help wanted: edge case lockfile fixtures for regression testing #528 fixture 1
  • Opposite of examples/wrong-parent/: 3-level chain where the intermediate parent range does not cover the OSV fix
  • Chain: express@4.22.1body-parser@1.20.4qs@6.14.2 (npm overrides isolate the deep path and pin vulnerable versions)
  • body-parser declares qs: ~6.14.0 — does not permit 6.15.2+
  • Documents fixture in examples/readme.md (also adds wrong-parent to the table)

Verified scan output

node dist/index.js examples/deep-chain-no-fix --verbose
  • 69 packages parsed from package-lock.json
  • 1 medium finding: qs@6.14.2 (transitive via express → body-parser → qs)
  • Fix command: npm install express@4.22.2 (parent upgrade)
  • Does not suggest npm update qs

Test plan

Closes Discussion #528 item fixture 1 (regression fixture).

Complements wrong-parent: express → body-parser → qs@6.14.2 where
body-parser@1.20.4 declares ~6.14.0 (does not cover 6.15.2+). CVE Lite
should suggest npm install express@4.22.2, not npm update qs.
@Ayush7614

Copy link
Copy Markdown
Contributor Author

cc: @sonukapoor

@sonukapoor sonukapoor left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested - correctly emits npm install express@4.22.2 (parent upgrade, not lockfile refresh) for the deep chain where the parent range doesn't cover the fix. Good complement to wrong-parent.

@sonukapoor sonukapoor merged commit ae09b6d into OWASP:main Jun 7, 2026
6 checks passed
@sonukapoor

Copy link
Copy Markdown
Collaborator

Merged — thank you @Ayush7614!

@sonukapoor sonukapoor mentioned this pull request Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants