[TSC] choose a npm publication method for the future
@alexander-akait is already working on this.
Since Aug 10, 2026.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 3
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
We started a discussion around the idea of using Trusted Publishing (ref), this issue is a more formal continuation of my comment:
Regarding trusted Publishing we did a great research and concluded that:
We believe Trusted Publishing represents the future, but it’s not yet ready for adoption in critical projects, as in its current state it wouldn’t prevent attacks such as Shai-Hulud and other recent ones.
https://openjsf.org/blog/publishing-securely-on-npm
Mostly due the missing step for 2FA confirming the publication. This will be fixed by npm once staged publishing is deployed (no ETA yet): https://github.blog/security/supply-chain-security/strengthening-supply-chain-security-preparing-for-the-next-malware-campaign/
In Express we are trying to do a CI version with 2FA (under discussion: https://github.com/expressjs/discussions/pull/443), so we can probably adopt it if we want to avoid local publication due bus factor
cc: @webpack/security-wg
Next steps
- Include TSC Meeting agenda label
Context
- Related to https://github.com/webpack/tsc/issues/86
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.
Assessment
This issue has not been assessed yet.