@atlaskit/tag
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @atlaskit/tag is a long-established Atlassian UI component package; the levenshtein match to 'pg' is purely coincidental and not a typosquat signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/css | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/link | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/avatar | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/motion | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/lozenge | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/spinner | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/teams-avatar | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-next | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party @atlaskit namespace dependency; expected for Atlaskit UI component packages. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 14.14.0 | 15 / 18 | |
| 14.13.3 | 15 / 17 | |
| 14.13.2 | 15 / 17 | |
| 14.13.1 | 15 / 17 | |
| 14.13.0 | 15 / 17 | |
| 14.12.1 | 15 / 17 | |
| 14.12.0 | 15 / 17 | |
| 14.11.0 | 15 / 17 | |
| 14.10.0 | 15 / 17 | |
| 14.9.1 | 15 / 17 | |
| 14.9.0 | 15 / 16 | |
| 14.8.1 | 15 / 16 | |
| 14.8.0 | 15 / 16 | |
| 14.7.1 | 15 / 16 | |
| 14.7.0 | 15 / 16 | |
| 14.6.2 | 14 / 15 | |
| 14.6.1 | 14 / 14 | |
| 14.6.0 | 14 / 14 | |
| 14.5.4 | 14 / 12 | |
| 14.5.3 | 14 / 11 | |
| 14.5.2 | 14 / 11 | |
| 14.5.1 | 14 / 11 | |
| 14.5.0 | 14 / 11 | |
| 14.4.0 | 14 / 11 | |
| 14.3.2 | 13 / 10 | |
| 14.3.1 | 13 / 10 | |
| 14.3.0 | 13 / 10 | |
| 14.2.6 | 12 / 10 | |
| 14.2.5 | 12 / 10 | |
| 14.2.4 | 12 / 10 | |
| 14.2.3 | 12 / 10 | |
| 14.2.2 | 12 / 10 | |
| 14.2.1 | 12 / 10 | |
| 14.2.0 | 12 / 10 | |
| 14.1.17 | 10 / 11 | |
| 14.1.16 | 11 / 12 | |
| 14.1.15 | 11 / 12 | |
| 14.1.14 | 11 / 12 | |
| 14.1.13 | 11 / 12 | |
| 14.1.12 | 11 / 12 | |
| 14.1.11 | 11 / 12 | |
| 14.1.10 | 11 / 12 | |
| 14.1.9 | 11 / 12 | |
| 14.1.8 | 11 / 12 | |
| 14.1.7 | 11 / 12 | |
| 14.1.6 | 11 / 12 | |
| 14.1.5 | 11 / 12 | |
| 14.1.4 | 11 / 12 | |
| 14.1.3 | 11 / 12 | |
| 14.1.2 | 11 / 13 | |
| 14.1.1 | 11 / 14 |
v14.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.