← Home

@platforma-open/platforma-open.titeseq-analysis

npm
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
bogus-package bogus-package AI (bogus-package): Meta/aggregator package pattern for platforma-open block system; tiny payload and no repo link are expected. ai
phantom-deps phantom-dep:@platforma-sdk/model AI (phantom-deps): Deps referenced via block.components config paths, not direct JS imports; stable false positive for this package type. ai
phantom-deps phantom-dep:@platforma-open/platforma-open.titeseq-analysis.ui AI (phantom-deps): Same org sub-package referenced via block config, not direct import. ai
phantom-deps phantom-dep:@platforma-open/platforma-open.titeseq-analysis.model AI (phantom-deps): Same org sub-package referenced via block config, not direct import. ai
phantom-deps phantom-dep:@platforma-open/platforma-open.titeseq-analysis.workflow AI (phantom-deps): Same org sub-package referenced via block config, not direct import. ai

Versions (showing 11 of 11)

Version Deps Published
2.1.5 4 / 1
2.1.4 4 / 1
2.1.3 4 / 1
2.1.2 4 / 1
2.1.1 4 / 1
2.1.0 4 / 1
2.0.4 4 / 1
2.0.3 4 / 1
2.0.2 4 / 1
2.0.1 4 / 1
2.0.0 4 / 1

v2.1.5

1 finding
LOW No provenance attestation provenance

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

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

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

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

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.