@atlaskit/empty-state
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 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 |
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.