Skip to content

Add FOSSA SCA scanning and dependency manifest registration [skip ci] - #5

Open
AmanRiat1 wants to merge 3 commits into
mainfrom
add-fossa-sca-scanning
Open

AmanRiat1 wants to merge 3 commits into
mainfrom
add-fossa-sca-scanning

Conversation

@AmanRiat1

Copy link
Copy Markdown

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

Chosen as the first of this batch because it is the simplest: npm, root package.json, package-lock.json present, single ecosystem.

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 main; 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.

Not ready to merge

The squad value in the manifest write is a placeholder and needs confirming before this merges, along with the corresponding registration on our side. Merging is what triggers the first manifest write, so the ordering matters.

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 and others added 2 commits September 1, 2026 18:08
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…p ci]

This repo publishes an artifact on push to its default branch, so merging the
onboarding change would also cut a release. Adding workflow_dispatch means the
merge can carry a skip-ci commit -- which suppresses every workflow on that
push, the publish one included -- and the scan plus manifest write can then be
run by hand against the default branch.

The update_manifest guard previously required github.event_name == 'push', so a
dispatched run would have scanned and silently skipped the write. It now accepts
either event while keeping the default-branch check, so dispatching against any
other ref still scans without writing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@AmanRiat1 AmanRiat1 changed the title Add FOSSA SCA scanning and dependency manifest registration Add FOSSA SCA scanning and dependency manifest registration [skip ci] Sep 3, 2026
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