Skip to content

Add FOSSA SCA scanning and dependency manifest registration - #4

Closed
AmanRiat1 wants to merge 1 commit into
mainfrom
DATAGO-150669-fossa-guardian-onboarding
Closed

AmanRiat1 wants to merge 1 commit into
mainfrom
DATAGO-150669-fossa-guardian-onboarding

Conversation

@AmanRiat1

@AmanRiat1 AmanRiat1 commented Sep 1, 2026 •

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.

First of the 10 solacecommunity repos in Annex A.10. Mirrors the validated
SolaceLabs pattern: a single root FOSSA scan (no matrix -- one repo, one FOSSA
project, one manifest row), and a manifest write guarded to push-on-trunk so
PR runs scan without writing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@AmanRiat1 AmanRiat1 changed the title DATAGO-150669: Add FOSSA SCA scanning and Guardian registration Add FOSSA SCA scanning and dependency manifest registration Sep 1, 2026
@AmanRiat1

Copy link
Copy Markdown
Author

Superseded by #5 — recreated on a cleanly-named branch.

@AmanRiat1 AmanRiat1 closed this Sep 1, 2026
@AmanRiat1
AmanRiat1 deleted the DATAGO-150669-fossa-guardian-onboarding branch September 1, 2026 21:45
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