@platforma-open/milaboratories.spatiotemporal-analysis
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@platforma-open/milaboratories.spatiotemporal-analysis.ui | AI (dependencies): Same-org sub-package dependency; part of the standard platforma block component pattern. | ai | |
| dependencies | unvetted-dep:@platforma-open/milaboratories.spatiotemporal-analysis.model | AI (dependencies): Same-org sub-package dependency; part of the standard platforma block component pattern. | ai | |
| dependencies | unvetted-dep:@platforma-open/milaboratories.spatiotemporal-analysis.workflow | AI (dependencies): Same-org sub-package dependency; part of the standard platforma block component pattern. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.spatiotemporal-analysis.ui | AI (phantom-deps): Deps referenced via block.components path strings, not direct imports — stable false positive for this package pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentional thin wrapper/aggregator; tiny payload and no description are structural, not spam indicators. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.spatiotemporal-analysis.model | AI (phantom-deps): Same block.components path-string reference pattern; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.spatiotemporal-analysis.workflow | AI (phantom-deps): Same block.components path-string reference pattern; not a direct import by design. | ai |
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.