@fluentui-react-native/radio-group
A cross-platform Radio Group 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 metadata gap; trusted bulk publisher, not a tampering indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party sibling package within same monorepo/org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft-owned monorepo with bot publisher; dormancy likely reflects release cadence, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft FluentUI React Native monorepo package published via bot; lack of Sigstore provenance is consistent across all versions and poses no material risk given the established publisher track record. | ai |
Versions (showing 51 of 410)
| Version | Deps | Published |
|---|---|---|
| 0.22.5 | 13 / 17 | |
| 0.22.4 | 12 / 18 | |
| 0.22.3 | 12 / 22 | |
| 0.22.1 | 12 / 22 | |
| 0.22.0 | 12 / 22 | |
| 0.21.31 | 12 / 17 | |
| 0.21.30 | 12 / 17 | |
| 0.21.29 | 12 / 17 | |
| 0.21.28 | 12 / 17 | |
| 0.21.27 | 12 / 17 | |
| 0.21.26 | 12 / 17 | |
| 0.21.25 | 13 / 13 | |
| 0.21.24 | 13 / 13 | |
| 0.21.23 | 13 / 13 | |
| 0.21.22 | 13 / 13 | |
| 0.21.21 | 13 / 13 | |
| 0.21.20 | 13 / 13 | |
| 0.21.19 | 13 / 13 | |
| 0.21.18 | 13 / 13 | |
| 0.21.17 | 13 / 11 | |
| 0.21.16 | 13 / 9 | |
| 0.21.15 | 13 / 9 | |
| 0.21.14 | 13 / 9 | |
| 0.21.13 | 13 / 9 | |
| 0.21.12 | 13 / 9 | |
| 0.21.11 | 13 / 9 | |
| 0.21.10 | 13 / 9 | |
| 0.21.9 | 13 / 9 | |
| 0.21.8 | 13 / 9 | |
| 0.21.7 | 13 / 9 | |
| 0.21.6 | 13 / 9 | |
| 0.21.5 | 13 / 9 | |
| 0.21.4 | 13 / 9 | |
| 0.21.3 | 13 / 9 | |
| 0.21.2 | 13 / 9 | |
| 0.21.1 | 13 / 9 | |
| 0.21.0 | 13 / 9 | |
| 0.20.17 | 13 / 8 | |
| 0.20.16 | 14 / 8 | |
| 0.20.15 | 14 / 8 | |
| 0.20.14 | 14 / 8 | |
| 0.20.13 | 14 / 8 | |
| 0.20.12 | 14 / 8 | |
| 0.20.11 | 14 / 8 | |
| 0.20.10 | 14 / 8 | |
| 0.20.9 | 14 / 8 | |
| 0.20.8 | 14 / 8 | |
| 0.20.7 | 14 / 8 | |
| 0.20.6 | 14 / 8 | |
| 0.20.5 | 14 / 8 | |
| 0.20.4 | 14 / 8 |
v0.22.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.21.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.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.
v0.21.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.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.