You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,6 +97,8 @@ That command writes generated reports into `reports/licenses/`.
97
97
98
98
Dependency review also runs automatically on pull requests to catch newly introduced vulnerable dependency changes.
99
99
100
+
That dependency review config also includes an allowlist for the licenses already present in the current dependency tree. If you intentionally add a dependency under a new acceptable license, update `.github/dependency-review-config.yml` in the same pull request.
101
+
100
102
## Changing the API Contract
101
103
102
104
If you modify request or response shapes:
@@ -131,6 +133,9 @@ If you modify request or response shapes:
131
133
5. Wait for the release workflow to verify the repo, publish GHCR images, and create the GitHub Release.
132
134
6. Confirm the release smoke workflow passes against the published images, or dispatch it manually for a tag if you need to re-check a release.
133
135
136
+
The release notes will also include links to the image provenance attestations generated during the publish workflow.
137
+
The release itself will also carry attached SPDX SBOM files for the source tree and the published runner images.
138
+
134
139
The component labels used by Release Drafter are synced from `.github/labels.json`, and most of the common ones are applied automatically from changed paths.
135
140
136
141
To run the same image smoke check locally, set `BACKEND_IMAGE` and `FRONTEND_IMAGE`, then run `npm run check:release-smoke`.
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,13 +127,19 @@ Pull requests also run GitHub dependency review so new vulnerable dependency cha
127
127
128
128
A separate GitHub workflow generates license-report artifacts for the root workspace, frontend workspace, and backend Python environment.
129
129
130
+
The dependency-review config also keeps a conservative allowlist of licenses already present in the current dependency tree, so tightening policy does not start by breaking routine updates.
131
+
132
+
An SBOM workflow also publishes SPDX artifacts for the repository source plus the frontend and backend runner images.
133
+
130
134
## Releases
131
135
132
136
- Release Drafter keeps a draft release updated from merged pull requests on `main` and can auto-label incoming pull requests by path.
133
137
- Path-based labels help sort PRs into frontend, backend, CI/CD, docs, and maintenance categories automatically.
134
138
- Release Drafter defaults to a patch bump unless a maintainer applies `minor` or `major` to the pull request.
135
139
- Pushing a tag like `v0.1.0` triggers the release workflow.
136
140
- That workflow verifies the tagged commit, publishes backend/frontend images to GHCR, and creates a GitHub Release with generated notes.
141
+
- The release workflow also generates build-provenance attestations for the published GHCR images and links them from the release notes.
142
+
- The GitHub Release also includes attached SPDX SBOM assets for the source tree and both runner images.
137
143
- A follow-up smoke workflow pulls those published GHCR images and checks backend health, a real inference request, and the frontend shell before you treat the release as healthy.
138
144
- Maintainers can re-run the same check manually with `BACKEND_IMAGE=... FRONTEND_IMAGE=... npm run check:release-smoke`.
Copy file name to clipboardExpand all lines: SECURITY.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,12 @@ The repository also uses automated scanning to help catch common security issues
33
33
- CodeQL code scanning on GitHub for JavaScript/TypeScript, Python, and workflow files
34
34
- GitHub dependency review on pull requests for newly introduced vulnerable dependency changes
35
35
- GitHub license-report artifacts for npm and Python dependency inventories
36
+
- GitHub SBOM artifacts for the repository source and runner images
37
+
- GitHub build-provenance attestations for published release images
38
+
39
+
Tagged releases also include attached SPDX SBOM files and release-note verification snippets for the published container images.
40
+
41
+
Dependency review is also configured with an allowlist that matches the current dependency tree, so changes that introduce new license types are surfaced deliberately instead of silently drifting in.
36
42
37
43
Those checks do not replace private disclosure. If you believe a vulnerability is real or
38
44
exploitable, please still report it through a private advisory.
0 commit comments