sourcefuse / sourcefuse/loopback4-audit-log
Use trusted OIDC publishing instead of token
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Since npm is strengthening its security need to use trusted OIDC publishing instead of token
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
Begin by finding the repository's npm publishing workflow and its token configuration, then compare them with npm's trusted OIDC publishing requirements. Done means releases use trusted OIDC publishing instead of a token and the workflow still publishes successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100