@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo CI publish quirk; publisher has long clean track record, no behavior change. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party sibling package in same monorepo. | ai | |
| 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 100 of 187)
| Version | Deps | Published |
|---|---|---|
| 0.11.5 | 8 / 14 | |
| 0.11.4 | 7 / 15 | |
| 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 | |
| 0.10.13 | 7 / 8 | |
| 0.10.12 | 7 / 8 | |
| 0.10.11 | 7 / 8 | |
| 0.10.10 | 7 / 8 | |
| 0.10.9 | 7 / 8 | |
| 0.10.8 | 7 / 8 | |
| 0.10.7 | 7 / 8 | |
| 0.10.6 | 7 / 8 | |
| 0.10.5 | 7 / 8 | |
| 0.10.4 | 7 / 8 | |
| 0.10.3 | 7 / 8 | |
| 0.10.2 | 7 / 8 | |
| 0.10.1 | 7 / 8 | |
| 0.10.0 | 7 / 8 | |
| 0.9.20 | 7 / 7 | |
| 0.9.19 | 7 / 7 | |
| 0.9.18 | 7 / 7 | |
| 0.9.17 | 7 / 7 | |
| 0.9.16 | 7 / 7 | |
| 0.9.15 | 7 / 7 | |
| 0.9.14 | 7 / 7 | |
| 0.9.13 | 7 / 7 | |
| 0.9.12 | 7 / 7 | |
| 0.9.11 | 7 / 7 | |
| 0.9.10 | 7 / 7 | |
| 0.9.9 | 7 / 7 | |
| 0.9.8 | 7 / 7 | |
| 0.9.7 | 7 / 7 | |
| 0.9.6 | 7 / 7 | |
| 0.9.5 | 7 / 7 | |
| 0.9.4 | 7 / 7 | |
| 0.9.3 | 7 / 7 | |
| 0.9.2 | 7 / 7 | |
| 0.9.1 | 7 / 7 | |
| 0.9.0 | 7 / 7 | |
| 0.8.29 | 7 / 6 | |
| 0.8.28 | 7 / 6 | |
| 0.8.27 | 7 / 6 | |
| 0.8.26 | 7 / 6 | |
| 0.8.25 | 7 / 6 | |
| 0.8.24 | 7 / 6 | |
| 0.8.23 | 7 / 6 | |
| 0.8.22 | 7 / 6 | |
| 0.8.21 | 7 / 6 | |
| 0.8.20 | 7 / 6 | |
| 0.8.19 | 7 / 6 | |
| 0.8.18 | 7 / 6 | |
| 0.8.17 | 7 / 6 | |
| 0.8.16 | 7 / 6 | |
| 0.8.15 | 7 / 6 | |
| 0.8.14 | 7 / 6 | |
| 0.8.13 | 7 / 6 | |
| 0.8.12 | 7 / 6 | |
| 0.8.11 | 7 / 6 | |
| 0.8.10 | 7 / 6 | |
| 0.8.9 | 7 / 6 | |
| 0.8.8 | 7 / 6 | |
| 0.8.7 | 7 / 6 | |
| 0.8.6 | 7 / 6 | |
| 0.8.5 | 7 / 6 | |
| 0.8.4 | 7 / 6 | |
| 0.8.3 | 7 / 6 | |
| 0.8.2 | 7 / 6 | |
| 0.8.1 | 7 / 6 | |
| 0.8.0 | 7 / 6 | |
| 0.7.50 | 7 / 7 | |
| 0.7.49 | 7 / 7 | |
| 0.7.48 | 7 / 7 | |
| 0.7.47 | 7 / 7 | |
| 0.7.46 | 7 / 7 | |
| 0.7.45 | 7 / 7 | |
| 0.7.43 | 7 / 7 | |
| 0.7.42 | 7 / 7 | |
| 0.7.41 | 7 / 7 | |
| 0.7.40 | 7 / 7 | |
| 0.7.39 | 7 / 7 | |
| 0.7.38 | 7 / 7 |
v0.11.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: uifrnbot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.45
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: uifrnbot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.