← Home

@platforma-open/milaboratories.clonotype-browser-3

npm
17
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mike-ainseldbolotin_mi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Aggregator/manifest package for platforma-open block ecosystem; tiny payload and no keywords are expected for this pattern. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.clonotype-browser-3.ui AI (phantom-deps): Referenced via block metadata config path, not direct JS import; stable false positive for this package type. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.clonotype-browser-3.model AI (phantom-deps): Referenced via block metadata config path, not direct JS import; stable false positive for this package type. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.clonotype-browser-3.workflow AI (phantom-deps): Referenced via block metadata config path, not direct JS import; stable false positive for this package type. ai
phantom-deps phantom-dep:@platforma-sdk/model AI (phantom-deps): SDK model referenced in config/metadata context, not direct JS import; stable false positive for this package type. ai

Versions (showing 17 of 17)

Version Deps Published
2.0.3 4 / 2
2.0.2 4 / 2
2.0.1 4 / 2
2.0.0 4 / 2
1.1.11 4 / 2
1.1.10 4 / 2
1.1.9 4 / 2
1.1.8 4 / 2
1.1.7 4 / 2
1.1.6 4 / 2
1.1.5 4 / 2
1.1.4 4 / 2
1.1.1 4 / 1
1.1.0 4 / 1
1.0.3 4 / 1
1.0.2 4 / 1
1.0.1 4 / 1

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.