@atlaskit/avatar
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
Keywords
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): Same-org @atlaskit scoped dependency; consistent with Atlassian monorepo component library pattern across all versions. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): Same-org @atlaskit scoped dependency; consistent with Atlassian monorepo component library pattern across all versions. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): Same-org @atlaskit scoped dependency; consistent with Atlassian monorepo component library pattern across all versions. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): Same-org @atlaskit scoped dependency; consistent with Atlassian monorepo component library pattern across all versions. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-next | AI (dependencies): Same-org @atlaskit scoped dependency; consistent with Atlassian monorepo component library pattern across all versions. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): Same-org @atlaskit scoped dependency; consistent with Atlassian monorepo component library pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@atlaskit/css | AI (phantom-deps): CSS/token deps in Atlaskit components are often consumed indirectly via build tooling; same-org scope, no security concern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Token deps in Atlaskit components are often consumed indirectly; same-org scope, no security concern. | ai |
Versions (showing 75 of 75)
| Version | Deps | Published |
|---|---|---|
| 25.15.1 | 9 / 23 | |
| 25.15.0 | 9 / 22 | |
| 25.14.2 | 9 / 22 | |
| 25.14.1 | 9 / 22 | |
| 25.14.0 | 9 / 22 | |
| 25.13.0 | 9 / 22 | |
| 25.12.0 | 9 / 22 | |
| 25.11.7 | 9 / 22 | |
| 25.11.6 | 9 / 22 | |
| 25.11.5 | 9 / 22 | |
| 25.11.4 | 9 / 22 | |
| 25.11.3 | 9 / 21 | |
| 25.11.2 | 9 / 21 | |
| 25.11.1 | 9 / 21 | |
| 25.11.0 | 10 / 21 | |
| 25.10.0 | 10 / 20 | |
| 25.9.2 | 10 / 18 | |
| 25.9.1 | 10 / 18 | |
| 25.9.0 | 10 / 18 | |
| 25.8.4 | 10 / 18 | |
| 25.8.3 | 10 / 18 | |
| 25.8.2 | 10 / 18 | |
| 25.8.1 | 10 / 18 | |
| 25.8.0 | 10 / 18 | |
| 25.7.5 | 10 / 18 | |
| 25.7.4 | 10 / 18 | |
| 25.7.3 | 10 / 18 | |
| 25.7.2 | 10 / 18 | |
| 25.7.1 | 10 / 18 | |
| 25.7.0 | 10 / 18 | |
| 25.6.3 | 10 / 18 | |
| 25.6.2 | 10 / 18 | |
| 25.6.1 | 10 / 18 | |
| 25.6.0 | 10 / 18 | |
| 25.5.6 | 10 / 18 | |
| 25.5.5 | 11 / 19 | |
| 25.5.4 | 11 / 19 | |
| 25.5.3 | 11 / 19 | |
| 25.5.2 | 11 / 19 | |
| 25.5.1 | 11 / 19 | |
| 25.5.0 | 11 / 19 | |
| 25.4.4 | 11 / 19 | |
| 25.4.3 | 11 / 19 | |
| 25.4.2 | 11 / 19 | |
| 25.4.1 | 11 / 19 | |
| 25.4.0 | 11 / 19 | |
| 25.3.2 | 11 / 19 | |
| 25.3.1 | 11 / 19 | |
| 25.3.0 | 11 / 19 | |
| 25.2.1 | 11 / 19 | |
| 25.2.0 | 11 / 19 | |
| 25.1.20 | 11 / 19 | |
| 25.1.19 | 11 / 19 | |
| 25.1.18 | 11 / 19 | |
| 25.1.17 | 11 / 19 | |
| 25.1.16 | 11 / 19 | |
| 25.1.15 | 11 / 19 | |
| 25.1.14 | 11 / 19 | |
| 25.1.13 | 11 / 19 | |
| 25.1.12 | 11 / 19 | |
| 25.1.11 | 11 / 19 | |
| 25.1.10 | 11 / 19 | |
| 25.1.9 | 11 / 20 | |
| 25.1.8 | 11 / 20 | |
| 25.1.7 | 11 / 20 | |
| 25.1.6 | 11 / 20 | |
| 25.1.5 | 11 / 20 | |
| 25.1.4 | 11 / 20 | |
| 25.1.3 | 11 / 20 | |
| 25.1.2 | 11 / 20 | |
| 25.1.1 | 11 / 20 | |
| 25.1.0 | 11 / 20 | |
| 25.0.5 | 11 / 20 | |
| 25.0.4 | 11 / 20 | |
| 25.0.3 | 11 / 20 |
v25.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.