@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, 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib-amd/index.js | AI (source-diff): AMD build bundle, not obfuscation; standard FluentUI dist output. | ai | |
| 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 4 of 104)
| Version | Deps | Published |
|---|---|---|
| 9.1.1 | 35 / 4 | |
| 9.1.0 | 35 / 4 | |
| 9.0.1 | 35 / 4 | |
| 9.0.0 | 35 / 4 |
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.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.