Skip to content

Add FOSSA SCA scanning and dependency manifest registration - #63

Merged
AmanRiat1 merged 1 commit into
masterfrom
add-fossa-sca-scanning
Sep 2, 2026
Merged

AmanRiat1 merged 1 commit into
masterfrom
add-fossa-sca-scanning

Conversation

@AmanRiat1

Copy link
Copy Markdown
Contributor

Adds FOSSA SCA scanning on master plus a build-manifest registration step, so this repo is covered by our automated dependency vulnerability tracking.

What this adds

File Purpose
.fossa.yml FOSSA project config
.github/workflow-config.json FOSSA policy/vulnerability both in REPORT mode — this gates nothing
.github/workflows/sca-scan-and-guard.yml Scan on PR + push to master; manifest write on push only

Non-blocking by design

REPORT mode means FOSSA findings are recorded, not enforced. This PR cannot start failing anyone else's builds.

The update_manifest job is guarded on github.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_path scopes 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.

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>
@AmanRiat1
AmanRiat1 merged commit 264e0e0 into master Sep 2, 2026
5 checks passed
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.

1 participant