← Home

@platforma-open/milaboratories.antibody-sequence-liabilities.workflow

npm

Block Workflow

9
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
provenance publisher-changed AI (provenance): mike-ainsel is an established publisher in the same org with 37 approved packages; transition appears legitimate. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by org-level publisher transition; no other risk signals present. ai
phantom-deps phantom-dep:@platforma-sdk/workflow-tengo AI (phantom-deps): Tengo workflow package; deps are build-time assets, not JS imports. Stable false positive for this package. ai
phantom-deps phantom-dep:@platforma-open/milaboratories.antibody-sequence-liabilities.liabilities-calc-script AI (phantom-deps): Same-org asset dependency used at build time, not imported as JS. Stable false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
6.0.1 2 / 1
6.0.0 2 / 1
5.1.0 2 / 1
5.0.1 2 / 1
5.0.0 2 / 1
4.3.0 2 / 1
4.2.0 2 / 1
4.1.0 2 / 1
4.0.0 2 / 1

v6.0.1

1 finding
LOW No provenance attestation provenance

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

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

v5.1.0

2 findings
HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-04-03) provenance

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

LOW No provenance attestation provenance

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

v5.0.1

2 findings
HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-03-26) provenance

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

LOW No provenance attestation provenance

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

v5.0.0

2 findings
HIGH Publisher changed: dbolotin_mi → mike-ainsel (on 2026-03-26) provenance

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

LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

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