@atlaskit/theme
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/ds-lib | AI (dependencies): Same-org (@atlaskit) dependency from Atlassian's design system monorepo; expected internal dependency for this package. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): Same-org (@atlaskit) dependency from Atlassian's design system monorepo; expected internal dependency for a theme package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org phantom dep in an Atlassian monorepo package; common pattern for transitive/peer resolution, not a risk signal. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 25.0.0 | 3 / 13 | |
| 24.0.0 | 3 / 13 | |
| 23.2.0 | 3 / 12 | |
| 23.1.0 | 3 / 12 | |
| 23.0.3 | 3 / 12 | |
| 23.0.2 | 3 / 12 | |
| 23.0.1 | 3 / 12 | |
| 23.0.0 | 3 / 12 | |
| 22.0.4 | 3 / 12 | |
| 22.0.3 | 3 / 11 | |
| 22.0.2 | 3 / 11 | |
| 22.0.1 | 3 / 11 | |
| 22.0.0 | 3 / 11 | |
| 21.0.5 | 3 / 11 | |
| 21.0.4 | 3 / 11 | |
| 21.0.3 | 3 / 11 | |
| 21.0.2 | 4 / 11 |
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.