← Home

@platforma-open/milaboratories.mixcr-scfv-clonotyping.workflow

npm
23
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
phantom-deps phantom-dep:@platforma-sdk/workflow-tengo AI (phantom-deps): Tengo workflow packages reference deps via config, not direct imports; stable FP for this package. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.software-mixcr AI (phantom-deps): Same-org dep referenced via Tengo config, not direct import; stable FP. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.software-repseqio AI (phantom-deps): Same-org dep referenced via Tengo config, not direct import; stable FP. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.software-ptransform AI (phantom-deps): Same-org dep referenced via Tengo config, not direct import; stable FP. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.mixcr-scfv-clonotyping.assemble-scfv AI (phantom-deps): Same-org dep referenced via Tengo config, not direct import; stable FP. ai

Versions (showing 23 of 23)

Version Deps Published
3.11.1 5 / 1
3.10.5 5 / 1
3.10.4 5 / 1
3.10.3 5 / 1
3.10.2 5 / 1
3.10.1 5 / 1
3.10.0 5 / 1
3.9.0 3 / 5
3.8.0 3 / 5
3.7.0 3 / 5
3.6.0 3 / 5
3.5.0 2 / 8
3.4.0 2 / 8
3.3.1 2 / 8
3.3.0 2 / 8
3.2.0 2 / 8
3.1.2 2 / 8
3.1.1 2 / 8
3.1.0 2 / 8
3.0.3 2 / 8
3.0.2 2 / 8
3.0.1 2 / 8
3.0.0 2 / 8

v3.11.1

1 finding
LOW No provenance attestation provenance

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

v3.10.5

1 finding
LOW No provenance attestation provenance

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

v3.10.4

1 finding
LOW No provenance attestation provenance

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

v3.10.3

1 finding
LOW No provenance attestation provenance

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

v3.10.2

1 finding
LOW No provenance attestation provenance

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

v3.10.1

1 finding
LOW No provenance attestation provenance

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

v3.10.0

1 finding
LOW No provenance attestation provenance

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

v3.9.0

1 finding
LOW No provenance attestation provenance

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

v3.8.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dbolotin_mi → mike-ainsel (on 2026-02-05, known maintainer) provenance

This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-05, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.7.0

1 finding
LOW No provenance attestation provenance

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

v3.6.0

1 finding
LOW No provenance attestation provenance

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

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.4.0

1 finding
LOW No provenance attestation provenance

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

v3.3.1

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

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