@atlaskit/smart-user-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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Atlassian publishes @atlaskit packages via their artifact team pipeline without Sigstore provenance; this is consistent across the entire @atlaskit namespace. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a standard Atlassian ecosystem npm alias for react-intl@^5.x, used consistently across the Atlaskit component library. Not a security risk. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-next | AI (dependencies): First-party Atlassian @atlaskit scoped dependency; part of the same official Atlassian frontend ecosystem as this package. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party Atlassian @atlaskit scoped dependency; part of the same official Atlassian frontend ecosystem as this package. | ai | |
| dependencies | unvetted-dep:@atlaskit/afm-i18n-platform-smart-experiences-smart-user-picker | AI (dependencies): First-party Atlassian i18n dependency for this specific component; published under the @atlaskit namespace by the same team. | ai | |
| dependencies | unvetted-dep:@atlaskit/user-picker | AI (dependencies): First-party Atlassian @atlaskit scoped dependency; part of the same official Atlassian frontend ecosystem as this package. | ai | |
| dependencies | unvetted-dep:@atlaskit/ufo | AI (dependencies): First-party Atlassian @atlaskit scoped dependency; part of the same official Atlassian frontend ecosystem as this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 10.2.0 | 9 / 13 | |
| 10.1.0 | 9 / 11 | |
| 10.0.5 | 9 / 11 | |
| 10.0.4 | 9 / 11 | |
| 10.0.3 | 9 / 11 | |
| 10.0.2 | 9 / 11 | |
| 10.0.1 | 9 / 11 | |
| 10.0.0 | 9 / 11 | |
| 9.2.1 | 10 / 10 | |
| 8.4.1 | 10 / 9 |
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.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.