Skip to content

trust: security policy, support window, private vulnerability reporting, Dependabot, signed checksums + provenance + SBOM on every release - #52

Merged
singhpratech merged 1 commit into
mainfrom
trust/security-policy-provenance
Sep 4, 2026
Merged

trust: security policy, support window, private vulnerability reporting, Dependabot, signed checksums + provenance + SBOM on every release#52
singhpratech merged 1 commit into
mainfrom
trust/security-policy-provenance

Conversation

@singhpratech

Copy link
Copy Markdown
Owner

The trust artefacts a platform or security review reads first.

  • SECURITY.md (and docs/community/security.md for the site): supported versions and the support window (current minor gets patch releases on every registry at once), private vulnerability reporting as the only channel (enabled on the repository today), acknowledgement within three business days and a thirty-day fix target, scope (bridge and bindings in; third-party drivers and servers out, recorded in UPSTREAM.md), and Verifying a download.
  • Release workflow, new trust job after every build: downloads the release's assets, writes SHA256SUMS, signs it with the release key (same key as Maven Central, 95CC478E1985A908), generates an SPDX SBOM of the source tree with anchore/sbom-action, records a build-provenance attestation for every asset with actions/attest-build-provenance (so gh attestation verify <file> --repo singhpratech/adbcbridge works), and attaches the three files. finish now requires it.
  • v0.1.0 already carries SHA256SUMS (attached today); its signature follows once signed offline.
  • .github/dependabot.yml: weekly updates for Actions, pip, cargo, nuget, maven and gomod.
  • README, docs index, FAQ, contributing, the three install pages (checksum step) and the roadmap link to the policy.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YG6wFApZpg2xe61EmKhaSZ

…rting, Dependabot, and a release job that signs SHA256SUMS, attests provenance and attaches an SBOM

SECURITY.md (and its docs copy under community/) states which versions get
fixes, how to report privately, the response targets, and how to verify a
download: SHA256SUMS on every release, plus from the next release a detached
GPG signature by the release key, a GitHub build-provenance attestation per
asset and an SPDX SBOM of the source tree. The release workflow gains a `trust`
job that produces those after every build; `finish` requires it. Dependabot
watches the six manifests. README, the docs index, the FAQ, contributing and
the three install pages link to it; the roadmap records it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YG6wFApZpg2xe61EmKhaSZ
@singhpratech
singhpratech merged commit 553b58e into main Sep 4, 2026
4 checks passed
@singhpratech
singhpratech deleted the trust/security-policy-provenance branch September 4, 2026 21:48
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