← Home

@atlaskit/inline-edit

67
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

Keywords

atlaskitreactui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@atlassian/react-compiler-gating AI (phantom-deps): Same Atlassian org scope; declared in config only, not imported at runtime. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Same-org @atlaskit scope phantom dep; stable false positive for this package family. ai
provenance no-provenance AI (provenance): Atlassian publishes via atlassianartifactteam with strong track record; lack of Sigstore provenance is not a risk signal for this established publisher. ai

Versions (showing 67 of 67)

Version Deps Published
16.2.4 14 / 17
16.2.3 14 / 17
16.2.2 14 / 17
16.2.1 14 / 17
16.2.0 14 / 17
16.1.0 14 / 17
16.0.1 14 / 17
16.0.0 13 / 18
15.6.16 13 / 17
15.6.15 13 / 17
15.6.14 13 / 17
15.6.13 13 / 17
15.6.12 13 / 16
15.6.11 14 / 16
15.6.10 14 / 16
15.6.9 14 / 16
15.6.8 14 / 15
15.6.7 14 / 15
15.6.6 14 / 15
15.6.5 14 / 15
15.6.4 14 / 15
15.6.3 14 / 15
15.6.2 14 / 15
15.6.1 14 / 15
15.6.0 14 / 15
15.5.0 14 / 15
15.4.2 14 / 15
15.4.1 14 / 15
15.4.0 14 / 15
15.3.21 14 / 15
15.3.20 14 / 15
15.3.19 15 / 17
15.3.18 15 / 17
15.3.17 15 / 17
15.3.16 15 / 17
15.3.15 15 / 17
15.3.14 15 / 17
15.3.13 15 / 17
15.3.12 15 / 17
15.3.11 15 / 17
15.3.10 15 / 17
15.3.9 15 / 17
15.3.8 15 / 17
15.3.7 15 / 17
15.3.6 15 / 17
15.3.5 15 / 17
15.3.4 15 / 18
15.3.3 15 / 19
15.3.2 15 / 19
15.3.1 15 / 19
15.3.0 15 / 19
15.2.6 15 / 19
15.2.5 15 / 19
15.2.4 15 / 19
15.2.3 15 / 19
15.2.2 15 / 19
15.2.1 15 / 19
15.2.0 15 / 19
15.1.5 15 / 19
15.1.4 15 / 19
15.1.3 15 / 19
15.1.2 15 / 19
15.1.1 15 / 19
15.1.0 15 / 19
15.0.2 15 / 19
15.0.1 15 / 19
15.0.0 15 / 19

v16.2.4

1 finding
INFO No provenance attestation provenance

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

v16.2.3

1 finding
INFO No provenance attestation provenance

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

v16.2.2

1 finding
INFO No provenance attestation provenance

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

v16.2.1

1 finding
INFO No provenance attestation provenance

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

v16.2.0

1 finding
INFO No provenance attestation provenance

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

v15.1.4

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.

v15.1.3

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.

v15.1.2

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.

v15.1.1

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.

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

v15.0.2

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.

v15.0.1

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.

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