Repository navigation
fix: use real packages in feeds-update stubs to avoid osv-scanner exit 127 - #43
Merged
pshickeydev merged 1 commit intoOct 28, 2026
Conversation
…t 127 osv-scanner v2.7.0 exits 127 when package resolution fails during a scan. The feeds-update stubs used fake package names (x, x/x) that cannot resolve in deps.dev, so every refresh attempt exited 127 and was reported as a download failure even when databases loaded fine. Use the same real package names with known advisories as the Containerfile build-time stub (requests, gin-gonic, lodash, log4j, rack, time, guzzle, Newtonsoft.Json). Verified in the built image: the scanner now exits 1 (vulnerabilities found — expected) instead of 127. Assisted-by: Claude Opus 4
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.
osv-scanner v2.7.0 exits 127 when package resolution fails during a scan.
The
feeds updatestubs used fake package names (x,x/x) that cannotresolve in deps.dev, so every runtime refresh attempt exited 127 and was
reported as a download failure even when the databases loaded fine:
Use the same real package names with known advisories as the Containerfile
build-time stub (requests, gin-gonic, lodash, log4j, rack, time, guzzle,
Newtonsoft.Json). Verified in the built
f474fc8image: the scanner nowexits 1 (vulnerabilities found — expected) instead of 127, so genuine
download failures are distinguishable from the expected scan outcome.
Follow-up to #42.
This PR description is AI-generated (Claude Opus 4).