rndm
random string generator
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): Publisher change from jongleberry to coderhaoxin occurred in 2015; coderhaoxin has a strong track record (316 approved, 0 rejected) and the transition aligns with the crypto-utils org. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): coderhaoxin was added as maintainer in 2015 alongside the publisher change; long-established legitimate transition with no adverse history. | ai |
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2015-10-27. 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.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.