@fluentui/react-bindings
A set of components and hooks to build components libraries and UI kits.
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:@fluentui/state | AI (dependencies): Internal FluentUI monorepo sibling dependency; expected and stable for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-northstar-styles-renderer | AI (dependencies): Same Microsoft FluentUI monorepo sibling package; not an independent risk. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft FluentUI monorepo package; provenance not yet configured but publisher is well-established. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.71.4 | 11 / 18 | |
| 0.71.3 | 11 / 18 | |
| 0.71.2 | 11 / 18 | |
| 0.71.1 | 11 / 18 | |
| 0.71.0 | 11 / 18 | |
| 0.70.0 | 11 / 18 | |
| 0.68.2 | 12 / 15 | |
| 0.68.0 | 12 / 15 | |
| 0.67.1 | 13 / 15 |
v0.71.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.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.70.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.68.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.
v0.68.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.67.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.