@atlaskit/link-picker
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/css | AI (phantom-deps): Declared dependency in monorepo component library; typical for Atlassian packages managing shared styles. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Declared dependency in monorepo component library; typical for Atlassian design token usage. | ai | |
| phantom-deps | phantom-dep:@react-loosely-lazy/manifest | AI (phantom-deps): Declared dependency referenced in config; legitimate for code-splitting in component library. | ai | |
| phantom-deps | phantom-dep:@atlaskit/afm-i18n-platform-linking-platform-link-picker | AI (phantom-deps): Declared i18n dependency; typical for Atlassian packages with internationalization support. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Atlaskit component packages routinely have minimal READMEs and no keywords; this is a structural pattern of the Atlassian Design System monorepo, not a spam indicator. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes @atlaskit packages without Sigstore provenance; this is consistent across the entire package family and not a security risk given the verified publisher track record. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 5.3.2 | 32 / 24 | |
| 5.3.1 | 32 / 24 | |
| 5.3.0 | 32 / 24 | |
| 5.2.1 | 32 / 24 | |
| 5.2.0 | 32 / 23 | |
| 5.1.7 | 32 / 23 | |
| 5.1.6 | 32 / 23 | |
| 5.1.5 | 32 / 23 | |
| 5.1.4 | 32 / 23 | |
| 5.1.3 | 32 / 23 | |
| 5.1.2 | 32 / 23 | |
| 5.1.1 | 33 / 22 | |
| 5.1.0 | 33 / 21 | |
| 5.0.1 | 33 / 21 | |
| 5.0.0 | 33 / 21 | |
| 4.2.24 | 32 / 20 | |
| 4.2.23 | 32 / 20 | |
| 4.2.22 | 32 / 20 | |
| 4.2.21 | 32 / 19 | |
| 4.2.20 | 32 / 19 | |
| 4.2.19 | 32 / 19 | |
| 4.2.18 | 32 / 19 | |
| 4.2.17 | 33 / 19 | |
| 4.2.16 | 33 / 19 | |
| 4.2.15 | 33 / 19 | |
| 4.2.14 | 33 / 19 | |
| 4.2.13 | 33 / 19 | |
| 4.2.12 | 33 / 19 | |
| 4.2.11 | 33 / 19 | |
| 4.2.10 | 33 / 19 | |
| 4.2.9 | 33 / 19 | |
| 4.2.8 | 33 / 19 | |
| 4.2.7 | 33 / 19 | |
| 4.2.6 | 33 / 19 | |
| 4.2.5 | 33 / 19 | |
| 4.2.4 | 33 / 19 | |
| 4.2.3 | 33 / 19 | |
| 4.2.2 | 33 / 19 | |
| 4.2.1 | 33 / 19 | |
| 4.2.0 | 33 / 19 | |
| 4.1.1 | 33 / 19 | |
| 4.1.0 | 33 / 19 | |
| 4.0.3 | 34 / 19 | |
| 4.0.2 | 34 / 19 | |
| 4.0.1 | 34 / 19 | |
| 4.0.0 | 34 / 19 | |
| 3.16.9 | 34 / 19 | |
| 3.16.8 | 34 / 19 | |
| 3.16.7 | 34 / 19 | |
| 3.16.6 | 34 / 19 | |
| 3.16.5 | 34 / 19 | |
| 3.16.4 | 34 / 19 |
v5.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.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.
v5.0.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.
v5.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.
v4.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.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.