Fail CI when dependencies in your lockfile lose npm provenance or trusted publisher status
-
Updated
Jul 27, 2026 - TypeScript
Fail CI when dependencies in your lockfile lose npm provenance or trusted publisher status
A composite GitHub Action that turns conventional commits into a draft release PR, tags the PR on merge, and stages publishing to npm via OIDC trusted publishing.
Consumer-side integrity verification for Ruby gems
Indexing support for Trusted Publishing on PyPI
A fast, conservative JSON repair library for malformed model output, hand-written config, and almost-JSON text. Repairs common syntax issues and returns clean Python objects.
Get trusted publishing and build reproducibility insights for any Rust supply chain
Trusted Publishing for Docker registries using GitHub Actions OIDC.
AI-assisted OSS maintainer workflows for PR review, issue triage, security triage, and release notes.
Easily compare the local devices windows release & build version, against broadly available official Windows 11 versioning. Detects silent updating-issues. This Repository also acts as the always up to date web-source of truth, it displays signed info accessible programmatically through designated GitHub pages.
[PoC] Trusted Publishing verifier for package URLs (purl)
Published npm artifact boundary for handshake-protocol-kernel; trusted publishing and MCP metadata.
🔒 Fail CI if dependencies in your lockfile lose npm provenance or trusted publisher status, enhancing the security of your projects.
Read-only scanner: is your npm/PyPI publish CI ready for OIDC trusted publishing? (post classic-token revocation, Dec 9 2025)
Checks if an npm package version was published via a Trusted Publisher (OIDC/Provenance)
Advanced GitHub Actions and package supply-chain defense platform for the May 2026 CI/CD compromise wave.
an example of using a trusted publishing (OIDC) to publish a package
Operational inventory, release policy, and audit tooling for BuiltByEcho npm packages
Preflight your GitHub Actions workflow for npm OIDC trusted publishing before the misleading 404/ENEEDAUTH at release time.
GitHub template for packing and publishing multi-target .NET NuGet packages via Trusted Publishing (OIDC) — clone-and-go CI/CD with optional container-based integration testing.
Add a description, image, and links to the trusted-publishing topic page so that developers can more easily learn about it.
To associate your repository with the trusted-publishing topic, visit your repo's landing page and select "manage topics."