← Home

@atlaskit/prosemirror-input-rules

40
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Atlassian publishes all @atlaskit packages without Sigstore provenance; this is consistent across their entire package portfolio and not a risk signal for this publisher. ai

Versions (showing 40 of 140)

Version Deps Published
3.6.27 4 / 1
3.6.26 4 / 1
3.6.25 4 / 1
3.6.24 4 / 1
3.6.23 4 / 1
3.6.22 4 / 1
3.6.21 4 / 1
3.6.20 4 / 1
3.6.19 4 / 1
3.6.18 4 / 1
3.6.17 4 / 1
3.6.16 4 / 1
3.6.15 4 / 1
3.6.14 4 / 1
3.6.13 4 / 1
3.6.12 4 / 1
3.6.11 4 / 1
3.6.10 4 / 1
3.6.9 4 / 1
3.6.8 4 / 1
3.6.7 4 / 1
3.6.6 4 / 1
3.6.5 4 / 1
3.6.4 4 / 1
3.6.3 4 / 1
3.6.2 4 / 1
3.6.1 4 / 1
3.6.0 4 / 1
3.5.0 3 / 1
3.4.2 2 / 1
3.4.1 2 / 1
3.4.0 2 / 1
3.3.0 2 / 1
3.2.3 2 / 1
3.2.2 2 / 1
3.2.1 2 / 1
3.2.0 2 / 1
3.1.1 2 / 2
3.1.0 2 / 2
3.0.0 2 / 2

v3.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.