@fluentui/react-components
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/react-alert | AI (dependencies): First-party @fluentui sub-package published by the same Microsoft/uifabricteam maintainer; unvetted status reflects pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@fluentui/react-infobutton | AI (dependencies): First-party @fluentui sub-package published by the same Microsoft/uifabricteam maintainer; unvetted status reflects pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@fluentui/react-virtualizer | AI (dependencies): First-party @fluentui sub-package published by the same Microsoft/uifabricteam maintainer; unvetted status reflects pipeline lag, not a security concern. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a standard implicit runtime dependency for SWC-compiled packages; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft/uifabricteam package with 1455 versions; lack of provenance attestation is not a meaningful risk signal here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 9.73.8 | 62 / 0 | |
| 9.73.7 | 62 / 0 | |
| 9.73.6 | 62 / 0 | |
| 9.73.5 | 62 / 0 | |
| 9.72.5 | 62 / 2 | |
| 9.72.2 | 62 / 2 | |
| 9.72.1 | 62 / 2 | |
| 9.72.0 | 62 / 2 | |
| 9.71.0 | 62 / 2 | |
| 9.69.0 | 62 / 2 | |
| 9.68.3 | 62 / 2 | |
| 9.68.2 | 62 / 2 | |
| 9.68.0 | 62 / 2 | |
| 9.67.0 | 62 / 2 | |
| 9.66.8 | 62 / 2 | |
| 9.66.5 | 62 / 2 | |
| 9.66.4 | 62 / 2 | |
| 9.66.3 | 62 / 2 | |
| 9.66.1 | 62 / 2 | |
| 9.66.0 | 62 / 2 | |
| 9.65.0 | 62 / 2 | |
| 9.64.1 | 61 / 2 | |
| 9.64.0 | 61 / 2 |
v9.73.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.73.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.73.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.73.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.72.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.72.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.72.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.72.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.71.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.69.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.68.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.68.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.68.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.67.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.66.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.66.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.66.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.66.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.66.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.66.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.65.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.64.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.64.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.