node-uuid
Rigorous implementation of RFC4122 (v1 and v4) UUIDs.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): broofa is the original author of node-uuid; the transition from coolaj86 back to broofa is a legitimate reclamation. GitHub repo URL has always pointed to broofa's namespace. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer changes reflect legitimate consolidation back to original author broofa; no malicious indicators. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): coolaj86 removal is part of the same legitimate transition back to original author broofa. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is consistent with a stable, mature UUID library. The publish aligns with a known maintainer transition back to the original author. | ai |
v1.4.8
2 findingsThis version was published by a different npm account than previous versions on 2017-03-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-11-12. This could indicate a legitimate maintainer transition or an account compromise.