@kmamal/numbers
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 5 approved packages; no material changes from prior version; consistent same-author ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Personal scoped math library; sparse docs are typical for this author's packages, not spam. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.14 | 2 / 1 | |
| 0.0.13 | 2 / 1 | |
| 0.0.12 | 2 / 1 | |
| 0.0.11 | 2 / 1 | |
| 0.0.10 | 2 / 1 | |
| 0.0.9 | 2 / 1 | |
| 0.0.8 | 2 / 1 | |
| 0.0.6 | 2 / 1 | |
| 0.0.5 | 2 / 1 |
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.