@atlaskit/side-navigation
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@atlaskit/css | AI (dependencies): First-party Atlassian org dependency; all @atlaskit/* packages are from the same publisher and ecosystem. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): First-party Atlassian org dependency; all @atlaskit/* packages are from the same publisher and ecosystem. | ai | |
| dependencies | unvetted-dep:@atlaskit/menu | AI (dependencies): First-party Atlassian org dependency; all @atlaskit/* packages are from the same publisher and ecosystem. | ai | |
| dependencies | unvetted-dep:@atlaskit/motion | AI (dependencies): First-party Atlassian org dependency; all @atlaskit/* packages are from the same publisher and ecosystem. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party Atlassian org dependency; all @atlaskit/* packages are from the same publisher and ecosystem. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): First-party Atlassian org dependency; all @atlaskit/* packages are from the same publisher and ecosystem. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party Atlassian org dependency; all @atlaskit/* packages are from the same publisher and ecosystem. | ai | |
| phantom-deps | phantom-dep:@atlaskit/css | AI (phantom-deps): Same-org phantom dep in a multi-entry-point package; benign pattern for Atlaskit design system packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org phantom dep in a multi-entry-point package; benign pattern for Atlaskit design system packages. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via their artifact team account with a strong track record; lack of Sigstore provenance is not disqualifying for this established publisher. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 11.2.2 | 10 / 22 | |
| 11.2.1 | 10 / 22 | |
| 11.2.0 | 10 / 22 | |
| 11.1.17 | 10 / 22 | |
| 11.1.16 | 10 / 22 | |
| 11.1.15 | 10 / 22 | |
| 11.1.14 | 10 / 22 | |
| 11.1.13 | 10 / 21 | |
| 11.1.12 | 10 / 21 | |
| 11.1.11 | 10 / 21 | |
| 11.1.10 | 10 / 21 | |
| 11.1.9 | 11 / 21 | |
| 11.1.8 | 11 / 21 | |
| 11.1.7 | 11 / 21 | |
| 11.1.6 | 11 / 21 | |
| 11.1.5 | 11 / 21 | |
| 11.1.4 | 11 / 21 | |
| 11.1.3 | 11 / 21 | |
| 11.1.2 | 11 / 21 | |
| 11.1.1 | 11 / 21 | |
| 11.1.0 | 11 / 21 | |
| 11.0.32 | 11 / 21 | |
| 11.0.31 | 11 / 21 | |
| 11.0.30 | 11 / 21 | |
| 11.0.29 | 11 / 21 | |
| 11.0.28 | 11 / 21 | |
| 11.0.27 | 11 / 21 | |
| 11.0.26 | 11 / 21 | |
| 11.0.25 | 11 / 21 | |
| 11.0.24 | 11 / 21 | |
| 11.0.23 | 11 / 21 | |
| 11.0.22 | 11 / 21 | |
| 11.0.21 | 11 / 21 | |
| 11.0.20 | 11 / 21 | |
| 11.0.19 | 11 / 21 | |
| 11.0.18 | 11 / 21 | |
| 11.0.17 | 11 / 21 | |
| 11.0.16 | 11 / 21 | |
| 11.0.15 | 11 / 21 | |
| 11.0.14 | 11 / 21 | |
| 11.0.13 | 11 / 21 | |
| 11.0.12 | 11 / 22 | |
| 11.0.11 | 11 / 23 | |
| 11.0.10 | 11 / 23 | |
| 11.0.9 | 11 / 23 | |
| 11.0.8 | 11 / 23 | |
| 11.0.7 | 11 / 23 | |
| 11.0.6 | 11 / 23 | |
| 11.0.5 | 11 / 23 | |
| 11.0.4 | 11 / 23 | |
| 11.0.3 | 11 / 23 | |
| 11.0.2 | 11 / 23 | |
| 11.0.1 | 11 / 23 | |
| 11.0.0 | 11 / 23 |
v11.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.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.
v11.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.
v11.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.