← Home

@platforma-open/milaboratories.top-antibodies.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): Workflow orchestration packages declare runtime deps for config-based loading, not direct imports. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.software-anarci AI (phantom-deps): Same-org dependency; stable pattern for this package family. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.top-antibodies.umap AI (phantom-deps): Same-org dependency; stable pattern for this package family. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.top-antibodies.spectratype AI (phantom-deps): Same-org dependency; stable pattern for this package family. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.top-antibodies.anarci-kabat AI (phantom-deps): Same-org dependency; stable pattern for this package family. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.top-antibodies.assembling-fasta AI (phantom-deps): Same-org dependency; stable pattern for this package family. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.top-antibodies.sample-clonotypes AI (phantom-deps): Same-org dependency; stable pattern for this package family. ai

Versions (showing 23 of 23)

Version Deps Published
4.2.0 7 / 1
4.1.2 7 / 1
4.1.1 7 / 1
4.1.0 7 / 1
4.0.3 7 / 1
4.0.2 7 / 1
4.0.1 7 / 1
4.0.0 7 / 1
3.0.1 7 / 1
3.0.0 7 / 1
2.2.2 7 / 1
2.2.1 7 / 1
1.17.3 7 / 1
1.17.2 7 / 1
1.17.1 7 / 1
1.17.0 7 / 3
1.16.0 7 / 3
1.15.1 7 / 3
1.15.0 7 / 3
1.14.1 7 / 3
1.14.0 7 / 3
1.13.2 7 / 3
1.13.1 7 / 3

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.2

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.3

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.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.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.

v2.2.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.

v2.2.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.

v1.17.3

1 finding
LOW No provenance attestation provenance

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

v1.17.1

1 finding
LOW No provenance attestation provenance

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

v1.17.0

1 finding
LOW No provenance attestation provenance

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

v1.16.0

1 finding
LOW No provenance attestation provenance

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

v1.15.1

1 finding
LOW No provenance attestation provenance

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

v1.15.0

1 finding
LOW No provenance attestation provenance

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

v1.14.1

1 finding
LOW No provenance attestation provenance

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

v1.14.0

1 finding
LOW No provenance attestation provenance

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

v1.13.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.13.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.