@platforma-open/milaboratories.rarefaction
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): mike-ainsel is an established publisher in the same org with 37 approved packages; transition appears legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentional aggregator/meta-package; tiny payload and no description are structural, not spam indicators. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.rarefaction.ui | AI (phantom-deps): Sub-packages referenced via block config path strings, not JS imports; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.rarefaction.model | AI (phantom-deps): Same as above; block config path reference, not a JS import. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.rarefaction.workflow | AI (phantom-deps): Same as above; block config path reference, not a JS import. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 3 / 1 | |
| 2.0.0 | 3 / 1 | |
| 1.0.19 | 3 / 1 | |
| 1.0.18 | 3 / 1 | |
| 1.0.17 | 3 / 1 | |
| 1.0.16 | 3 / 1 | |
| 1.0.15 | 3 / 1 | |
| 1.0.14 | 3 / 1 | |
| 1.0.13 | 3 / 1 | |
| 1.0.12 | 3 / 1 | |
| 1.0.11 | 3 / 1 | |
| 1.0.10 | 3 / 1 |
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.
v1.0.19
2 findingsThis version was published by a different npm account than previous versions on 2026-04-03. 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.0.18
2 findingsThis version was published by a different npm account than previous versions on 2026-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.
v1.0.17
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. 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.0.16
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. 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.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.