mheap / mheap/pin-github-action
Ensure Github Provenance from pipelines to npm
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 184
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Howdy!
Thanks for the great action. I would like to request that you ensure the npm publish pipeline is fully compliant with Github Provenance API.
https://github.blog/security/supply-chain-security/introducing-npm-package-provenance/
Example: https://www.npmjs.com/package/nestjs-otel (Scroll down to provenance)
Ledger entry example: https://search.sigstore.dev/?logIndex=249778415
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the npm publish pipeline in the repository's GitHub Actions configuration and compare its behavior with the linked GitHub Provenance API and npm provenance examples. Done means published packages expose verifiable GitHub provenance and the resulting ledger entry can be checked through Sigstore.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100