@platforma-open/milaboratories.peptide-profiling
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Thin aggregator/manifest package for platforma-open block ecosystem; tiny payload and missing top-level metadata are structural, not spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Description lives in block.meta.description; top-level omission is a pattern across this org's packages. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/model | AI (phantom-deps): Used in block config/manifest, not directly imported in JS — stable false positive for this package type. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.peptide-profiling.ui | AI (phantom-deps): Referenced via block.components config path, not JS import — stable false positive. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.peptide-profiling.model | AI (phantom-deps): Referenced via block.components config path, not JS import — stable false positive. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.peptide-profiling.workflow | AI (phantom-deps): Referenced via block.components config path, not JS import — stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 4 / 1 | |
| 1.1.3 | 4 / 1 | |
| 1.1.2 | 4 / 1 | |
| 1.1.1 | 4 / 1 | |
| 1.1.0 | 4 / 1 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.