@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 100 of 104)
| Version | Deps | Published |
|---|---|---|
| 9.74.4 | 62 / 0 | |
| 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 | |
| 9.61.2 | 61 / 2 | |
| 9.37.4 | 50 / 4 | |
| 9.37.3 | 50 / 4 | |
| 9.37.2 | 50 / 4 | |
| 9.37.1 | 50 / 4 | |
| 9.37.0 | 50 / 4 | |
| 9.36.0 | 50 / 4 | |
| 9.35.1 | 49 / 4 | |
| 9.35.0 | 49 / 4 | |
| 9.34.3 | 48 / 4 | |
| 9.34.2 | 48 / 4 | |
| 9.34.1 | 48 / 4 | |
| 9.34.0 | 48 / 4 | |
| 9.33.0 | 47 / 4 | |
| 9.32.3 | 47 / 4 | |
| 9.32.1 | 47 / 4 | |
| 9.31.1 | 47 / 4 | |
| 9.31.0 | 47 / 4 | |
| 9.30.4 | 47 / 4 | |
| 9.30.3 | 47 / 4 | |
| 9.30.2 | 47 / 4 | |
| 9.30.1 | 47 / 4 | |
| 9.30.0 | 47 / 4 | |
| 9.29.5 | 47 / 4 | |
| 9.29.4 | 47 / 4 | |
| 9.29.3 | 47 / 4 | |
| 9.29.2 | 47 / 4 | |
| 9.29.1 | 47 / 4 | |
| 9.29.0 | 47 / 4 | |
| 9.28.1 | 47 / 4 | |
| 9.28.0 | 47 / 4 | |
| 9.27.4 | 47 / 4 | |
| 9.27.3 | 47 / 4 | |
| 9.27.2 | 47 / 4 | |
| 9.27.1 | 47 / 4 | |
| 9.27.0 | 47 / 4 | |
| 9.26.2 | 47 / 4 | |
| 9.26.1 | 47 / 4 | |
| 9.26.0 | 47 / 4 | |
| 9.25.1 | 47 / 4 | |
| 9.25.0 | 47 / 4 | |
| 9.24.0 | 47 / 4 | |
| 9.23.1 | 46 / 4 | |
| 9.23.0 | 46 / 4 | |
| 9.22.1 | 46 / 4 | |
| 9.22.0 | 46 / 4 | |
| 9.21.0 | 46 / 4 | |
| 9.20.4 | 45 / 4 | |
| 9.20.3 | 45 / 4 | |
| 9.20.2 | 45 / 4 | |
| 9.20.1 | 45 / 4 | |
| 9.20.0 | 45 / 4 | |
| 9.19.1 | 45 / 4 | |
| 9.19.0 | 45 / 4 | |
| 9.18.9 | 45 / 4 | |
| 9.18.8 | 45 / 4 | |
| 9.18.7 | 45 / 4 | |
| 9.18.6 | 45 / 4 | |
| 9.18.5 | 45 / 4 | |
| 9.18.4 | 45 / 4 | |
| 9.18.3 | 45 / 4 | |
| 9.7.1 | 42 / 4 | |
| 9.7.0 | 41 / 4 | |
| 9.6.3 | 41 / 4 | |
| 9.6.2 | 41 / 4 | |
| 9.6.1 | 41 / 4 | |
| 9.6.0 | 41 / 4 | |
| 9.5.3 | 41 / 4 | |
| 9.5.2 | 40 / 4 | |
| 9.5.1 | 40 / 4 | |
| 9.5.0 | 40 / 4 | |
| 9.4.0 | 39 / 4 | |
| 9.3.2 | 38 / 4 | |
| 9.3.1 | 38 / 4 | |
| 9.3.0 | 38 / 4 | |
| 9.2.0 | 37 / 4 |
v9.74.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.61.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.37.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.37.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.37.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.35.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.34.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.34.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.32.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.30.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.30.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.29.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.29.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.27.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.27.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
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.0
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.