@fluentui/react-radio
Fluent UI Radio component
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is Microsoft's official CSS-in-JS library for Fluent UI, published from the same org. Stable dependency for all @fluentui/* packages. | ai | |
| dependencies | unvetted-dep:@fluentui/react-field | AI (dependencies): Sibling package from the microsoft/fluentui monorepo; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-label | AI (dependencies): Sibling package from the microsoft/fluentui monorepo; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): Sibling package from the microsoft/fluentui monorepo; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): Sibling package from the microsoft/fluentui monorepo; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): Sibling package from the microsoft/fluentui monorepo; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): Sibling package from the microsoft/fluentui monorepo; legitimate internal dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): Sibling package from the microsoft/fluentui monorepo; legitimate internal dependency. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft/fluentui monorepo does not use Sigstore provenance attestation; this is consistent across all versions and not a risk indicator for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 9.6.3 | 9 / 0 | |
| 9.6.2 | 9 / 0 | |
| 9.6.1 | 9 / 0 | |
| 9.6.0 | 9 / 0 | |
| 9.5.16 | 9 / 0 | |
| 9.5.15 | 9 / 0 | |
| 9.5.14 | 9 / 0 | |
| 9.5.13 | 9 / 0 | |
| 9.5.12 | 9 / 4 | |
| 9.5.11 | 9 / 4 | |
| 9.5.10 | 9 / 4 | |
| 9.5.9 | 9 / 4 | |
| 9.5.8 | 9 / 4 | |
| 9.5.7 | 9 / 4 | |
| 9.5.6 | 9 / 4 | |
| 9.5.5 | 9 / 4 | |
| 9.5.4 | 9 / 4 | |
| 9.5.3 | 9 / 4 | |
| 9.5.2 | 9 / 4 | |
| 9.5.1 | 9 / 4 | |
| 9.5.0 | 9 / 4 | |
| 9.4.7 | 9 / 4 | |
| 9.4.6 | 9 / 4 | |
| 9.4.5 | 9 / 4 | |
| 9.4.4 | 9 / 4 | |
| 9.4.3 | 9 / 4 | |
| 9.4.2 | 9 / 4 | |
| 9.4.1 | 9 / 4 | |
| 9.4.0 | 9 / 4 | |
| 9.3.9 | 9 / 4 | |
| 9.3.8 | 9 / 4 | |
| 9.3.7 | 9 / 4 |
v9.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.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.
v9.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.
v9.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.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.