@atlaskit/section-message
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 @atlaskit org dependency; normal composition pattern for Atlassian component library packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): First-party @atlaskit org dependency; normal composition pattern for Atlassian component library packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/link | AI (dependencies): First-party @atlaskit org dependency; normal composition pattern for Atlassian component library packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/button | AI (dependencies): First-party @atlaskit org dependency; normal composition pattern for Atlassian component library packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party @atlaskit org dependency; normal composition pattern for Atlassian component library packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/heading | AI (dependencies): First-party @atlaskit org dependency; normal composition pattern for Atlassian component library packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): First-party @atlaskit org dependency; normal composition pattern for Atlassian component library packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party @atlaskit org dependency; normal composition pattern for Atlassian component library packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Tokens declared but not directly imported is a common pattern in @atlaskit monorepo packages where tokens are used transitively via other @atlaskit deps. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via atlassianartifactteam with a strong track record; lack of Sigstore provenance is common and not a risk indicator here. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 8.13.0 | 9 / 15 | |
| 8.12.15 | 9 / 15 | |
| 8.12.14 | 9 / 15 | |
| 8.12.13 | 9 / 15 | |
| 8.12.12 | 9 / 15 | |
| 8.12.11 | 9 / 14 | |
| 8.12.10 | 9 / 14 | |
| 8.12.9 | 9 / 14 | |
| 8.12.8 | 10 / 14 | |
| 8.12.7 | 10 / 13 | |
| 8.12.6 | 10 / 13 | |
| 8.12.5 | 10 / 13 | |
| 8.12.4 | 10 / 13 | |
| 8.12.3 | 10 / 13 | |
| 8.12.2 | 10 / 13 | |
| 8.12.1 | 10 / 13 | |
| 8.12.0 | 10 / 13 | |
| 8.11.3 | 10 / 13 | |
| 8.11.2 | 10 / 13 | |
| 8.11.1 | 10 / 13 | |
| 8.11.0 | 10 / 13 | |
| 8.10.0 | 10 / 13 | |
| 8.9.4 | 10 / 13 | |
| 8.9.3 | 10 / 13 | |
| 8.9.2 | 10 / 13 | |
| 8.9.1 | 10 / 13 | |
| 8.9.0 | 10 / 13 | |
| 8.8.1 | 11 / 14 | |
| 8.8.0 | 11 / 14 | |
| 8.7.8 | 11 / 14 | |
| 8.7.7 | 11 / 14 | |
| 8.7.6 | 11 / 14 | |
| 8.7.5 | 11 / 14 | |
| 8.7.4 | 11 / 14 | |
| 8.7.3 | 11 / 14 | |
| 8.7.2 | 11 / 14 | |
| 8.7.1 | 11 / 14 | |
| 8.7.0 | 11 / 14 | |
| 8.6.1 | 11 / 14 | |
| 8.6.0 | 11 / 14 | |
| 8.5.2 | 11 / 14 | |
| 8.5.1 | 11 / 15 | |
| 8.5.0 | 11 / 15 | |
| 8.4.0 | 11 / 14 | |
| 8.3.0 | 10 / 15 | |
| 8.2.10 | 10 / 15 | |
| 8.2.9 | 10 / 15 | |
| 8.2.8 | 10 / 15 | |
| 8.2.7 | 10 / 15 | |
| 8.2.6 | 10 / 15 | |
| 8.2.5 | 10 / 15 | |
| 8.2.4 | 10 / 15 |
v8.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.12.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.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.
v8.12.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.
v8.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.