@fluentui-react-native/dropdown
A cross-platform Dropdown component using the Fluent Design System
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): uifrnbot is a Microsoft monorepo automation account predating widespread Sigstore provenance adoption; absence of attestation is expected and stable for this package family. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.11.3 | 7 / 18 | |
| 0.11.1 | 7 / 18 | |
| 0.11.0 | 7 / 18 | |
| 0.10.31 | 7 / 13 | |
| 0.10.30 | 7 / 13 | |
| 0.10.29 | 7 / 13 | |
| 0.10.28 | 7 / 13 | |
| 0.10.27 | 7 / 13 | |
| 0.10.26 | 7 / 13 | |
| 0.10.25 | 7 / 13 | |
| 0.10.24 | 7 / 13 | |
| 0.10.23 | 7 / 13 | |
| 0.10.22 | 7 / 12 | |
| 0.10.21 | 7 / 12 | |
| 0.10.20 | 7 / 12 | |
| 0.10.19 | 7 / 12 | |
| 0.10.18 | 7 / 12 | |
| 0.10.17 | 7 / 12 | |
| 0.10.16 | 7 / 12 | |
| 0.10.15 | 7 / 12 | |
| 0.10.14 | 7 / 10 |
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.
v0.10.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.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.
v0.10.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.