Support Trusted publishing for Github Actions Self-Hosted Runners
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 777
- Forks
- 267
- PR merge metrics
- No merged PRs in 30d
Description
Self hosted runners are an essential security and performance stance for any reasonable organization.
Ignoring this use-case in the trusted publisher is a huge gap. It forces people to downgrade their security to use trusted publishing, or to do other kinds of hacks, or perhaps even deprecating npmjs as a publishing platform.
I was double surprised to learn that this isn't tracked or covered by any issue, bug. The docs say something about "future versions", but don't contain any insight to what that exactly means.
Contributor guide
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
No files, tests, or entry points are named. Start by reviewing the npm/rfcs repository's RFC process and the trusted publishing documentation referenced in the issue; define the self-hosted GitHub Actions runner use case, required changes, and acceptance criteria so support can be proposed and assessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100