|
|
Log in / Subscribe / Register

Is this our chance to stop using NPM?

Is this our chance to stop using NPM?

Posted Jun 2, 2026 20:58 UTC (Tue) by mathstuf (subscriber, #69389)
In reply to: Is this our chance to stop using NPM? by dsommers
Parent article: Multiple redhat-cloud-services npm packages compromised (StepSecurity Blog)

The Red Hat advisory says "a compromised GitHub account". So existing mechanisms:

- 2FA (already possible)
- branch protections (already possible)
- require signed commits (possible?)
- require signed pushes (possible?)


to post comments

Is this our chance to stop using NPM?

Posted Jun 2, 2026 22:29 UTC (Tue) by dsommers (subscriber, #55274) [Link]

A compromised GH account is likely. But it might also include an API token key approach, where 2FA does not help much.

Signed commits, tags and pushes, which would need to be verified to complete a build process, is one good way. Or pulling two (or more) independent git repositories (not automatically mirrored ones) and verify branches/tags matches would be another way.

Is this our chance to stop using NPM?

Posted Jun 4, 2026 16:21 UTC (Thu) by cortana (subscriber, #24596) [Link]

According to this description:

npm binds trusted publishing to a repository plus a workflow filename, not to a branch

... making the repo the unit of trust. I celebrate NPM's bold decision to enforce the concept of Git as a distributed system of repos, rather than the centralized model favoured by enterprises of a single repo with branch protection rules...


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds