@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, 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 |
|---|---|---|---|---|
| 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 100 of 171)
| Version | Deps | Published |
|---|---|---|
| 9.6.4 | 9 / 0 | |
| 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 | |
| 9.3.6 | 9 / 4 | |
| 9.3.5 | 9 / 4 | |
| 9.3.4 | 9 / 4 | |
| 9.3.3 | 9 / 4 | |
| 9.3.2 | 9 / 4 | |
| 9.3.1 | 9 / 4 | |
| 9.3.0 | 9 / 4 | |
| 9.2.42 | 9 / 4 | |
| 9.2.41 | 9 / 4 | |
| 9.2.40 | 9 / 4 | |
| 9.2.39 | 9 / 4 | |
| 9.2.38 | 9 / 4 | |
| 9.2.37 | 9 / 4 | |
| 9.2.36 | 9 / 4 | |
| 9.2.35 | 9 / 4 | |
| 9.2.34 | 9 / 5 | |
| 9.2.33 | 9 / 5 | |
| 9.2.32 | 9 / 5 | |
| 9.2.31 | 9 / 5 | |
| 9.2.30 | 9 / 5 | |
| 9.2.29 | 9 / 5 | |
| 9.2.28 | 9 / 5 | |
| 9.2.27 | 9 / 5 | |
| 9.2.26 | 9 / 5 | |
| 9.2.25 | 9 / 5 | |
| 9.2.24 | 9 / 5 | |
| 9.2.23 | 9 / 5 | |
| 9.2.22 | 9 / 5 | |
| 9.2.21 | 9 / 5 | |
| 9.2.20 | 9 / 5 | |
| 9.2.19 | 9 / 5 | |
| 9.2.18 | 9 / 5 | |
| 9.2.17 | 9 / 5 | |
| 9.2.16 | 9 / 5 | |
| 9.2.15 | 9 / 5 | |
| 9.2.14 | 9 / 5 | |
| 9.2.13 | 9 / 5 | |
| 9.2.12 | 9 / 5 | |
| 9.2.11 | 9 / 5 | |
| 9.2.10 | 9 / 5 | |
| 9.2.9 | 9 / 5 | |
| 9.2.8 | 9 / 5 | |
| 9.2.7 | 9 / 5 | |
| 9.2.6 | 9 / 5 | |
| 9.2.5 | 9 / 5 | |
| 9.2.4 | 9 / 5 | |
| 9.2.3 | 9 / 5 | |
| 9.2.2 | 9 / 5 | |
| 9.2.1 | 9 / 5 | |
| 9.2.0 | 9 / 5 | |
| 9.1.61 | 10 / 5 | |
| 9.1.60 | 10 / 5 | |
| 9.1.59 | 10 / 5 | |
| 9.1.58 | 10 / 5 | |
| 9.1.57 | 10 / 5 | |
| 9.1.56 | 10 / 5 | |
| 9.1.55 | 10 / 5 | |
| 9.1.54 | 10 / 5 | |
| 9.1.53 | 10 / 5 | |
| 9.1.52 | 10 / 5 | |
| 9.1.51 | 10 / 5 | |
| 9.1.50 | 10 / 5 | |
| 9.1.49 | 10 / 5 | |
| 9.1.48 | 10 / 5 | |
| 9.1.47 | 10 / 5 | |
| 9.1.46 | 10 / 5 | |
| 9.1.45 | 10 / 5 |
v9.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.18
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.2.17
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.2.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.
v9.2.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.
v9.2.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.
v9.2.13
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.2.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.2.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.2.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.2.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.2.8
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.2.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.
v9.2.6
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.2.5
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.2.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.
v9.2.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.
v9.2.2
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.2.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.2.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.1.61
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.1.60
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.1.59
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.1.58
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.1.57
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.1.56
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.1.55
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.1.54
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.1.53
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.1.52
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.1.51
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.1.50
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.1.49
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.1.48
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.1.47
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.1.46
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.1.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.