Repository navigation
build(deps): pin the built-in plugins that declare requirements and access - #536
Conversation
…ccess All nine compiled-in plugins are released on bomly-sdk v0.16.0, with their descriptors' Requires and their manifests' access blocks: depsdev-license-matcher v0.4.0, govulncheck-analyzer v0.5.0, grype-matcher v0.8.0, jsreach-analyzer v0.5.0, jvmreach-analyzer v0.5.0, osv-matcher v0.4.0, pyreach-analyzer v0.5.0, scorecard-matcher v0.4.0, syft-detector v0.7.0. The four reachability analyzers declare source-tree-v1, dependency-graph-v1 and vulnerability-records-v1, so preflight now applies to them. Naming one explicitly on an SBOM target stops with exit 4 before any stage runs. The matchers and the syft detector declare none, so their behavior is unchanged. make generate shows no drift. Refs bomly-dev/bomly-planning#51. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Upgrade plugin dependencies go.mod |
Nine direct bomly-plugin-* dependencies receive version upgrades. jvmreach-analyzer moves from v0.4.1 to v0.5.0. |
Priority:
Estimated code review effort: 1 (Trivial) | ~4 minutes
Change: Other
Possibly related PRs
- bomly-dev/bomly-cli#530: Both PRs update the
jvmreach-analyzerrequirement ingo.mod; this PR advances it beyond the version set by#530. - bomly-dev/bomly-cli#531:
#531adds preflight checks for component requirements, which the supplied context links to the analyzer requirements associated with this PR.
Merge Risk: 
Minimal · up to a62ea
-
No actionable merge-blocking risk is established.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
Bomly Diff SummaryCompared Overview
Dependency ChangesSummary: 0 added, 9 version changed, 0 detail changes, 0 removed. Changed Dependencies
Vulnerabilities✅ No vulnerability changes. License ChangesSummary: 0 added, 9 changed, 0 removed. Changed Licenses
Project Posture✅ No project posture changes ( Policy FindingsSummary: 9 introduced, 0 persisted, 0 resolved. Introduced Findings
|
This is the last CLI step of bomly-dev/bomly-planning#51 before v0.30.0. It pins the nine compiled-in plugins to their releases on bomly-sdk v0.16.0.
RequiresEvery plugin's
bomly-plugin.jsonnow carries anaccessblock. That matters for the managed archives; the compiled-in path is unaffected.Verified end to end on the lite build:
bomly scan --path sbom.cdx.json --sbom --enrich --matchers osv --analyze --analyzers govulncheckexits 4 with: analyzer govulncheck requires source-tree-v1: the target is an SBOM document, not a source tree; scan a directory with --path or a Git repository with --url.--path <go module>runs normally and exits 0.Checks:
make test,make build-liteand lint all pass.make generateshows no drift: the generated component pages cover detectors, matchers and auditors, and none of the built-ins of those kinds declares requirements.🤖 Generated with Claude Code
Summary by CodeRabbit