@atlaskit/link
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:pino | AI (typosquat): @atlaskit/link is a scoped Atlassian Design System package; the levenshtein match to 'pino' is a false positive with no plausible confusion vector. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): @atlaskit/tokens is a same-org design token package; phantom dep finding is a minor code quality issue, not a security concern. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 6 / 13 | |
| 3.4.2 | 6 / 12 | |
| 3.4.1 | 6 / 12 | |
| 3.4.0 | 6 / 12 | |
| 3.3.4 | 6 / 12 | |
| 3.3.3 | 6 / 10 | |
| 3.3.2 | 6 / 10 | |
| 3.3.1 | 6 / 10 | |
| 3.3.0 | 6 / 10 | |
| 3.2.17 | 6 / 10 | |
| 3.2.16 | 6 / 10 | |
| 3.2.15 | 6 / 10 | |
| 3.2.14 | 6 / 10 | |
| 3.2.13 | 6 / 10 | |
| 3.2.12 | 6 / 10 | |
| 3.2.11 | 6 / 10 | |
| 3.2.10 | 6 / 10 | |
| 3.2.9 | 6 / 10 | |
| 3.2.8 | 6 / 10 | |
| 3.2.7 | 6 / 10 | |
| 3.2.6 | 6 / 10 | |
| 3.2.5 | 6 / 10 | |
| 3.2.4 | 6 / 11 | |
| 3.2.3 | 6 / 11 | |
| 3.2.2 | 6 / 11 | |
| 3.2.1 | 6 / 11 | |
| 3.2.0 | 6 / 11 | |
| 3.1.0 | 6 / 11 | |
| 3.0.2 | 6 / 11 | |
| 3.0.1 | 6 / 11 | |
| 3.0.0 | 6 / 11 |
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.