← Home

@atlaskit/empty-state

29
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
phantom-deps phantom-dep:@atlassian/react-compiler-gating AI (phantom-deps): Same Atlassian org scope; config-only reference, not a runtime import. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Same org scope (@atlaskit); phantom dep is likely a build-time or transitive usage, not a supply chain risk for this well-established Atlassian package. ai
provenance no-provenance AI (provenance): Atlassian publishes via atlassianartifactteam with a strong track record; lack of Sigstore provenance is common and not a disqualifying signal here. ai

Versions (showing 29 of 29)

Version Deps Published
11.1.4 8 / 11
11.1.3 8 / 11
11.1.2 8 / 11
11.1.1 8 / 11
11.1.0 8 / 11
11.0.1 8 / 11
11.0.0 7 / 12
10.2.0 7 / 11
10.1.17 7 / 11
10.1.16 7 / 11
10.1.15 7 / 11
10.1.14 7 / 10
10.1.13 7 / 9
10.1.12 7 / 9
10.1.11 7 / 9
10.1.10 7 / 9
10.1.9 8 / 11
10.1.8 8 / 11
10.1.7 8 / 11
10.1.6 8 / 11
10.1.5 8 / 11
10.1.4 8 / 11
10.1.3 8 / 12
10.1.2 8 / 12
10.1.1 8 / 12
10.1.0 8 / 12
10.0.2 8 / 12
10.0.1 8 / 12
10.0.0 8 / 12

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

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

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

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