umd
Universal Module Definition for use in automated build systems
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 | missing-githead | AI (provenance): Same long-standing maintainer; no material code/dep changes in this version. Likely a publish tooling change. | ai | |
| phantom-deps | phantom-dep:ruglify | AI (phantom-deps): ruglify is declared in dependencies and used via config/indirect reference; not a phantom dependency concern. | ai | |
| provenance | publisher-changed | AI (provenance): forbeslindesay is the original author per repo URL and package.json; legitimate publisher resuming control of their own package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by many years; no security concern for this established package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.0.3 | 0 / 4 | |
| 3.0.2 | 0 / 4 | |
| 3.0.1 | 0 / 4 | |
| 3.0.0 | 0 / 4 | |
| 2.1.0 | 4 / 2 | |
| 2.0.0 | 4 / 2 | |
| 1.3.1 | 4 / 2 | |
| 1.3.0 | 4 / 2 | |
| 1.2.1 | 4 / 1 | |
| 1.2.0 | 4 / 1 | |
| 1.1.1 | 4 / 0 | |
| 1.1.0 | 4 / 0 | |
| 1.0.0 | 4 / 0 |
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsThis version was published by a different npm account than previous versions on 2018-03-12. 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.
v3.0.1
2 findingsThis version was published by a different npm account than previous versions on 2015-04-25. 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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: forbeslindesay.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: forbeslindesay.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.