md5
js function for hashing messages with MD5
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
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 coolaj86 to pvorb (the listed author and GitHub repo owner) occurred in 2015; well-established legitimate transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): pvorb is the package author and GitHub repo owner; maintainer addition is legitimate and stable. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): charenc, crypt, is-buffer are standard crypto-utility deps for an MD5 implementation; expected for this package. | ai | |
| dependencies | unvetted-dep:crypt | AI (dependencies): crypt ~0.0.1 is a long-standing, stable dependency of md5 across all versions; not a newly introduced or suspicious dependency. | ai | |
| provenance | no-provenance | AI (provenance): md5 is a mature, widely-trusted package; lack of Sigstore provenance is expected for packages of this age and does not indicate risk. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 3 / 2 | |
| 2.2.1 | 3 / 1 | |
| 2.2.0 | 3 / 1 | |
| 2.1.0 | 3 / 1 | |
| 2.0.0 | 3 / 1 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2015-07-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.