convert-units
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Historical 2018 transfer, stable and long-approved since. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same historical transfer, not a fresh takeover signal. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale 3118-day-old change, inconsistent with takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Old dormancy gap tied to same historical transfer. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.3.4 | 2 / 2 | |
| 2.3.3 | 2 / 2 | |
| 2.3.2 | 2 / 2 | |
| 2.3.1 | 2 / 2 | |
| 2.3.0 | 2 / 2 | |
| 2.2.0 | 2 / 2 | |
| 2.1.0 | 2 / 2 | |
| 2.0.1 | 2 / 2 | |
| 2.0.0 | 2 / 1 |
v2.3.3
2 findingsThis version was published by a different npm account (jiminikiz) than the most recent previously approved version (benng) on 2018-01-12. It has since remained available on npm for 3116 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
2 findingsThis version was published by a different npm account (jiminikiz) than the most recent previously approved version (benng) on 2018-01-10. It has since remained available on npm for 3118 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.