@atlaskit/badge
A badge is a visual indicator for numeric values such as tallies and scores.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Atlassian's atlassianartifactteam publisher has 110 approved packages; lack of Sigstore provenance is a known gap for this publisher, not a security risk. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): @atlaskit/tokens is a first-party Atlaskit design token package; phantom usage is expected in design system components using CSS-based token references. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 18.6.0 | 5 / 13 | |
| 18.5.0 | 5 / 13 | |
| 18.4.6 | 5 / 13 | |
| 18.4.5 | 5 / 13 | |
| 18.4.4 | 5 / 13 | |
| 18.4.3 | 5 / 13 | |
| 18.4.2 | 5 / 12 | |
| 18.4.1 | 5 / 11 | |
| 18.4.0 | 5 / 11 | |
| 18.3.4 | 5 / 11 | |
| 18.3.3 | 5 / 11 | |
| 18.3.2 | 5 / 11 | |
| 18.3.1 | 5 / 11 | |
| 18.3.0 | 5 / 11 | |
| 18.2.4 | 6 / 12 | |
| 18.2.3 | 6 / 12 | |
| 18.2.2 | 6 / 12 | |
| 18.2.1 | 6 / 12 | |
| 18.2.0 | 6 / 12 | |
| 18.1.6 | 6 / 12 | |
| 18.1.5 | 6 / 12 | |
| 18.1.4 | 6 / 13 | |
| 18.1.3 | 6 / 13 | |
| 18.1.2 | 6 / 13 |
v18.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.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.
v18.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.