@atlaskit/linking-common
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): @atlaskit/tokens is in the same Atlassian org scope; phantom dep finding is a stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian's atlassianartifactteam publisher consistently publishes without Sigstore provenance; this is a stable characteristic of their release pipeline, not a risk indicator. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): Same Atlassian org scope; unvetted status reflects review pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/json-ld-types | AI (dependencies): Same Atlassian org scope; unvetted status reflects review pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/linking-types | AI (dependencies): Same Atlassian org scope; unvetted status reflects review pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-next | AI (dependencies): Same Atlassian org scope; unvetted status reflects review pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): Same Atlassian org scope; unvetted status reflects review pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@compiled/react | AI (dependencies): @compiled/react is Atlassian's own CSS-in-JS library, consistently used across the @atlaskit/* ecosystem. Not a security concern. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 9.13.0 | 9 / 13 | |
| 9.12.2 | 9 / 13 | |
| 9.12.1 | 9 / 13 | |
| 9.12.0 | 9 / 13 | |
| 9.11.6 | 9 / 13 | |
| 9.11.5 | 9 / 11 | |
| 9.11.4 | 9 / 11 | |
| 9.11.3 | 9 / 11 | |
| 9.11.2 | 9 / 11 | |
| 9.11.1 | 9 / 11 | |
| 9.11.0 | 10 / 11 | |
| 9.10.1 | 10 / 11 | |
| 9.10.0 | 10 / 11 | |
| 9.9.3 | 10 / 11 | |
| 9.9.2 | 10 / 11 | |
| 9.9.1 | 10 / 12 | |
| 9.9.0 | 11 / 12 | |
| 9.8.4 | 11 / 12 | |
| 9.8.3 | 11 / 12 | |
| 9.8.2 | 11 / 12 | |
| 9.8.1 | 11 / 12 | |
| 9.8.0 | 11 / 12 | |
| 9.7.5 | 11 / 12 | |
| 9.7.4 | 11 / 12 | |
| 9.7.3 | 11 / 12 | |
| 9.7.2 | 11 / 12 | |
| 9.7.1 | 11 / 12 | |
| 9.7.0 | 11 / 12 | |
| 9.6.0 | 11 / 12 | |
| 9.5.7 | 11 / 11 | |
| 9.5.6 | 11 / 11 | |
| 9.5.5 | 11 / 11 | |
| 9.5.4 | 11 / 11 | |
| 9.5.3 | 11 / 11 | |
| 9.5.2 | 11 / 11 | |
| 9.5.1 | 11 / 11 | |
| 9.5.0 | 11 / 11 | |
| 9.4.0 | 11 / 11 | |
| 9.3.0 | 11 / 11 | |
| 9.2.3 | 11 / 11 | |
| 9.2.2 | 11 / 12 | |
| 9.2.1 | 11 / 12 | |
| 9.2.0 | 11 / 12 | |
| 9.1.4 | 11 / 12 | |
| 9.1.3 | 11 / 12 | |
| 9.1.2 | 11 / 12 | |
| 9.1.1 | 11 / 12 | |
| 9.1.0 | 11 / 12 | |
| 9.0.4 | 11 / 12 | |
| 9.0.3 | 11 / 12 | |
| 9.0.2 | 11 / 12 | |
| 9.0.1 | 11 / 12 | |
| 9.0.0 | 11 / 12 |
v9.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.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.
v9.11.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.
v9.11.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.
v9.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.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.
v9.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.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.