@platforma-open/milaboratories.antibody-sequence-liabilities
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 with 37 approved packages in the same org; transition appears legitimate. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.antibody-sequence-liabilities.ui | AI (phantom-deps): Deps referenced via block.components path strings, not JS imports; stable pattern for this package family. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.antibody-sequence-liabilities.model | AI (phantom-deps): Same block.components path-string pattern; not a JS import. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.antibody-sequence-liabilities.workflow | AI (phantom-deps): Same block.components path-string pattern; not a JS import. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentionally minimal meta/aggregator package; tiny payload and no description are expected for this block-registry pattern. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 5.0.5 | 3 / 1 | |
| 5.0.4 | 3 / 1 | |
| 5.0.3 | 3 / 1 | |
| 5.0.2 | 3 / 1 | |
| 5.0.1 | 3 / 1 | |
| 5.0.0 | 3 / 1 | |
| 4.0.3 | 3 / 1 | |
| 4.0.2 | 3 / 1 | |
| 4.0.1 | 3 / 1 | |
| 4.0.0 | 3 / 1 | |
| 3.2.1 | 3 / 1 | |
| 3.2.0 | 3 / 1 | |
| 3.1.0 | 3 / 1 | |
| 3.0.2 | 3 / 1 | |
| 3.0.1 | 3 / 1 | |
| 3.0.0 | 3 / 1 | |
| 2.4.17 | 3 / 1 |
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
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.
v4.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. 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.
v4.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. 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.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. 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.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.