Add FOSSA SCA scanning and dependency manifest registration - #63
Merged
Merged
Conversation
Adds a single root FOSSA scan (no matrix -- one repo, one FOSSA project, one manifest row) plus a manifest write guarded to push-on-default-branch, so pull request runs scan without writing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Adds FOSSA SCA scanning on
masterplus a build-manifest registration step, so this repo is covered by our automated dependency vulnerability tracking.What this adds
.fossa.yml.github/workflow-config.jsonREPORTmode — this gates nothing.github/workflows/sca-scan-and-guard.ymlmaster; manifest write on push onlyNon-blocking by design
REPORTmode means FOSSA findings are recorded, not enforced. This PR cannot start failing anyone else's builds.The
update_manifestjob is guarded ongithub.event_name == 'push' && github.ref_name == github.event.repository.default_branch, so it does not run on pull requests — only the scan does.Pattern notes
Mirrors the equivalent setup already merged and passing across our other public repos. One thing carried over deliberately: no scan matrix.
fossa.only_pathscopes what is scanned, but the project id comes from--project, so matrix entries all upload into one project and overwrite each other, while the manifest emits one row per entry — producing registrations that point at FOSSA projects which never exist. A root scan resolves every ecosystem in one pass. One repo, one FOSSA project, one manifest row.