Replace path traversal hack with $REGISTRY_PATH and $REGISTRY_MODULE_PATH env vars#287
Merged
fproulx-boostsecurity merged 2 commits intomainfrom Jan 26, 2026
Merged
Conversation
…$REGISTRY_MODULE_PATH env vars Uses the new env vars from boostsec-scanner-cli#285: - $REGISTRY_MODULE_PATH for same-module file references - $REGISTRY_PATH for cross-module file references Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Trivy crashes (exit code 2, goroutine dump) when scanning google/osv-scanner. This is a trivy runtime issue unrelated to the registry path changes. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
scott-boost
approved these changes
Jan 26, 2026
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.
Summary
$SETUP_PATH/../../registry/path traversal hack with the new$REGISTRY_PATHand$REGISTRY_MODULE_PATHenv vars introduced in boostsecurityio/boostsec-scanner-cli#285$REGISTRY_MODULE_PATHfor same-module file references (gitleaks, gosec, trivy-fs, osv-scanner, npm-audit, bundler-audit)$REGISTRY_PATHfor cross-module file references (gitleaks-full→gitleaks, trivy-sbom→trivy-fs, boost-sca→trivy-fs)osv-scannertest fixture fromtrivy-sbom/tests.yamlas it was causing tests to be unreliable (Trivy is unable to handle such a complex codebase, resulting in a goroutine stack overflow — there is no known fix in Trivy for this)Modules updated
gitleaks- boost.toml copygitleaks-full- boost.toml copy (from gitleaks module)trivy-fs- prescan_checks.sh copy + filelist.txt referencetrivy-sbom- prescan_checks.sh copy (from trivy-fs)boost-sca- prescan_checks.sh copy (from trivy-fs)gosec- prescan_checks.sh copyosv-scanner- prescan_checks.sh copy + filelist.txt referencenpm-audit- prescan_checks.sh copybundler-audit- prescan_checks.sh copyTest plan
gitleaksscan locally — boost.toml copied correctly via$REGISTRY_MODULE_PATHtrivy-fsscan locally — prescan_checks.sh works with$REGISTRY_PATHfilelist referencegosecprescan check locally — correctly detects missing Go files via$REGISTRY_MODULE_PATH🤖 Generated with Claude Code