56,966 blogs · 4,417,066 posts Claim your blog

Record · corpus.blog/posts/01a08784-c839-7365-bcba-779948cb73f7

How GitHub could secure npm

Human Who Codes - Human Who Codes · published 6 January 2026

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at humanwhocodes.com Wayback capture

1blogs citing

First cited: 29 Jan 2026
Most recent: 29 Jan 2026
Rank this month: not ranked
Links from this post: 10
Words captured: 2,661

Cited by

Blog

In the post

Date

Securing npm is table stakes Read at the source ↗

29 Jan 2026

Links from this post

Link

Host

https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack

socket.dev

https://socket.dev/blog/tinycolor-supply-chain-attack-affects-40-packages

socket.dev

https://github.blog/security/supply-chain-security/our-plan-for-a-more-secure-npm-supply-chain/

github.blog

https://jfrog.com/blog/new-compromised-packages-in-largest-npm-attack-in-history/

jfrog.com

https://socket.dev/blog/nx-supply-chain-attack-investigation-github-actions-workflow-exploit

socket.dev

https://docs.npmjs.com/about-access-tokens

docs.npmjs.com

https://repos.openssf.org/trusted-publishers-for-all-package-repositories

repos.openssf.org

https://socket.dev/blog/ongoing-supply-chain-attack-targets-crowdstrike-npm-packages

socket.dev

Publishing More Securely on npm: Guidance from the OpenJS Security Collaboration Space Read at the source ↗

https://github.com/orgs/community/discussions/179562

github.com