@platforma-open/milaboratories.mixcr-amplicon-alignment
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 (730 approved) in the same org; transition appears legitimate. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Platforma block manifest packages consistently omit npm description; metadata is in the block.meta field instead. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org sub-packages (model/ui/workflow) — standard block assembly pattern for this publisher. | ai | |
| phantom-deps | phantom-dep:@platforma-sdk/model | AI (phantom-deps): Used in block config metadata, not direct JS imports; stable false positive for this package type. | ai | |
| dependencies | unvetted-dep:@platforma-open/milaboratories.mixcr-amplicon-alignment.workflow | AI (dependencies): Same-org sub-package dependency; consistent with this package's documented modular block structure. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate block-registry package; tiny payload and missing top-level description are structural, not spam indicators. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.mixcr-amplicon-alignment.workflow | AI (phantom-deps): Same monorepo block pattern; not a JS import but a block component reference. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.mixcr-amplicon-alignment.model | AI (phantom-deps): Same monorepo block pattern; not a JS import but a block component reference. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.mixcr-amplicon-alignment.ui | AI (phantom-deps): Sub-package dependency referenced via block manifest path, not JS import; stable false positive for this package family. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 1.8.28 | 3 / 1 | |
| 1.8.27 | 3 / 1 | |
| 1.8.26 | 3 / 1 | |
| 1.8.25 | 3 / 1 | |
| 1.8.24 | 3 / 1 | |
| 1.8.23 | 3 / 1 | |
| 1.8.22 | 3 / 1 | |
| 1.8.21 | 3 / 1 | |
| 1.8.20 | 3 / 1 | |
| 1.8.19 | 3 / 1 | |
| 1.8.18 | 3 / 1 | |
| 1.8.17 | 3 / 1 | |
| 1.8.16 | 3 / 1 | |
| 1.8.15 | 3 / 1 | |
| 1.8.14 | 3 / 1 | |
| 1.8.13 | 3 / 1 | |
| 1.8.12 | 3 / 1 | |
| 1.8.11 | 3 / 1 | |
| 1.8.10 | 3 / 1 | |
| 1.8.9 | 3 / 1 | |
| 1.8.8 | 3 / 1 | |
| 1.8.7 | 3 / 1 | |
| 1.8.6 | 3 / 1 | |
| 1.8.5 | 3 / 1 | |
| 1.8.4 | 3 / 1 | |
| 1.8.3 | 3 / 1 | |
| 1.8.2 | 3 / 1 | |
| 1.8.1 | 3 / 1 | |
| 1.8.0 | 3 / 1 | |
| 1.7.1 | 3 / 1 | |
| 1.7.0 | 3 / 1 | |
| 1.6.0 | 3 / 1 | |
| 1.5.0 | 4 / 1 | |
| 1.4.2 | 4 / 1 | |
| 1.4.1 | 4 / 1 | |
| 1.4.0 | 4 / 1 | |
| 1.3.11 | 4 / 1 | |
| 1.3.10 | 4 / 1 | |
| 1.3.9 | 4 / 1 | |
| 1.3.8 | 4 / 1 | |
| 1.3.7 | 4 / 1 | |
| 1.3.6 | 4 / 1 | |
| 1.3.5 | 4 / 1 | |
| 1.3.4 | 4 / 1 | |
| 1.3.3 | 4 / 1 | |
| 1.3.1 | 4 / 1 | |
| 1.3.0 | 4 / 1 | |
| 1.2.0 | 4 / 1 | |
| 1.1.0 | 4 / 1 | |
| 1.0.7 | 4 / 1 | |
| 1.0.6 | 4 / 1 | |
| 1.0.5 | 4 / 1 | |
| 1.0.4 | 4 / 1 | |
| 1.0.3 | 4 / 1 | |
| 1.0.2 | 4 / 1 | |
| 1.0.1 | 4 / 1 | |
| 1.0.0 | 0 / 3 |
v1.8.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. 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.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.