@atlaskit/select
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @atlaskit/top-layer; consistent with normal Atlaskit internal dependency evolution. | ai | |
| phantom-deps | phantom-dep:@atlaskit/spinner | AI (phantom-deps): Phantom dependency within same Atlaskit org scope; typical for monorepo component libraries. | ai | |
| dependencies | unvetted-dep:@atlaskit/theme | AI (dependencies): First-party Atlassian design system dependency; expected and legitimate for this UI component package. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party Atlassian design system dependency; expected and legitimate for this UI component package. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): First-party Atlassian design system dependency; expected and legitimate for this UI component package. | ai | |
| dependencies | unvetted-dep:@atlaskit/react-select | AI (dependencies): First-party Atlassian fork of react-select; core dependency for this select component package. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-next | AI (dependencies): First-party Atlassian analytics library; standard dependency across the @atlaskit component suite. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): First-party Atlassian design system dependency; expected and legitimate for this UI component package. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Referenced in config files in a monorepo context; not a runtime import concern for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org monorepo package; phantom dep finding is expected in Atlassian's build setup. | ai | |
| phantom-deps | phantom-dep:@atlaskit/primitives | AI (phantom-deps): Same-org monorepo package; phantom dep finding is expected in Atlassian's build setup. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via their artifact team pipeline without Sigstore provenance; consistent across their entire package suite. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party Atlassian feature flag utility; standard dependency across the @atlaskit component suite. | ai | |
| dependencies | unvetted-dep:@popperjs/core | AI (dependencies): @popperjs/core is a well-known, widely-used positioning library; legitimate dependency for a select/dropdown component. | ai |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 21.12.9 | 18 / 26 | |
| 21.12.8 | 18 / 26 | |
| 21.12.7 | 18 / 26 | |
| 21.12.6 | 18 / 26 | |
| 21.12.5 | 18 / 26 | |
| 21.12.4 | 18 / 26 | |
| 21.12.3 | 18 / 25 | |
| 21.12.2 | 18 / 25 | |
| 21.12.1 | 18 / 25 | |
| 21.12.0 | 18 / 25 | |
| 21.11.0 | 18 / 25 | |
| 21.10.5 | 17 / 24 | |
| 21.10.4 | 17 / 24 | |
| 21.10.3 | 17 / 24 | |
| 21.10.2 | 17 / 24 | |
| 21.10.1 | 17 / 23 | |
| 21.10.0 | 17 / 23 | |
| 21.9.0 | 17 / 23 | |
| 21.8.4 | 17 / 23 | |
| 21.8.3 | 17 / 23 | |
| 21.8.2 | 17 / 23 | |
| 21.8.1 | 17 / 22 | |
| 21.8.0 | 17 / 22 | |
| 21.7.8 | 17 / 22 | |
| 21.7.7 | 17 / 22 | |
| 21.7.6 | 17 / 22 | |
| 21.7.5 | 17 / 22 | |
| 21.7.4 | 17 / 22 | |
| 21.7.3 | 17 / 22 | |
| 21.7.2 | 16 / 21 | |
| 21.7.1 | 16 / 21 | |
| 21.7.0 | 16 / 21 | |
| 21.6.4 | 16 / 21 | |
| 21.6.3 | 16 / 21 | |
| 21.6.2 | 16 / 21 | |
| 21.6.1 | 16 / 21 | |
| 21.6.0 | 16 / 21 | |
| 21.5.0 | 16 / 21 | |
| 21.4.3 | 16 / 21 | |
| 21.4.2 | 16 / 21 | |
| 21.4.1 | 17 / 21 | |
| 21.4.0 | 17 / 21 | |
| 21.3.10 | 17 / 21 | |
| 21.3.9 | 17 / 21 | |
| 21.3.8 | 17 / 21 | |
| 21.3.7 | 17 / 21 | |
| 21.3.6 | 17 / 21 | |
| 21.3.5 | 17 / 21 | |
| 21.3.4 | 17 / 21 | |
| 21.3.3 | 17 / 21 | |
| 21.3.2 | 17 / 21 |
v21.12.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.10.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.
v21.10.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.
v21.10.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.
v21.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.10.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.
v21.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.8.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.
v21.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.7.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.
v21.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.6.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.
v21.6.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.
v21.5.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.
v21.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.