mafintosh / mafintosh/why-is-node-running
Version 3.2.2 package not signed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
I have `trustPolicy: no-downgrade` set in my pnpm-workspace.yaml file and pnpm gives the error:
> ERR_PNPM_TRUST_DOWNGRADE High-risk trust downgrade for "why-is-node-running@3.2.2" (possible package takeover)
I'm pretty sure it's because 3.2.0 & 3.2.1 were "Built and signed on GitHub Actions" [according to npmjs](https://www.npmjs.com/package/why-is-node-running/v/3.2.0#provenance) and have a checkmark in the versions list, whereas 3.2.2 does not.
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
Compare the npm provenance for why-is-node-running versions 3.2.0, 3.2.1, and 3.2.2, starting with the package links in the issue and the pnpm-workspace.yaml trustPolicy setting. Trace the release configuration used for the affected package; done when version 3.2.2 has the expected signing provenance and no-downgrade no longer reports a trust downgrade.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100