← Home

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

npm

Block model

11
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
dependencies unvetted-dep:@types/lodash.omit AI (dependencies): @types/lodash.omit is a standard DefinitelyTyped package; stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Scoped monorepo package from MiLaboratories org; missing metadata is a style choice, not a spam indicator. ai
phantom-deps phantom-dep:lodash.omit AI (phantom-deps): lodash.omit is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@types/lodash.omit AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. ai

Versions (showing 11 of 11)

Version Deps Published
2.0.3 4 / 5
2.0.2 4 / 5
2.0.1 4 / 5
2.0.0 4 / 5
1.3.0 4 / 5
1.2.0 4 / 5
1.1.4 4 / 5
1.1.3 3 / 5
1.1.0 3 / 6
1.0.2 3 / 6
1.0.1 3 / 6

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.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.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.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.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.1.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.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.