@fluentui/react-theme
Fluent UI themes
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:@fluentui/tokens | AI (dependencies): Sibling package in the Microsoft FluentUI monorepo; same trusted publisher ecosystem. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a standard implicit runtime dependency for SWC-compiled packages; its presence as a declared-but-not-directly-imported dep is expected and stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft Fluent UI package published by uifabricteam; lack of Sigstore provenance is not a risk signal for this well-known package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 9.2.1 | 2 / 0 | |
| 9.2.0 | 2 / 2 | |
| 9.1.19 | 2 / 3 | |
| 9.1.18 | 2 / 3 | |
| 9.1.17 | 2 / 3 | |
| 9.1.16 | 2 / 3 | |
| 9.1.15 | 2 / 3 | |
| 9.1.14 | 2 / 3 | |
| 9.1.13 | 2 / 3 | |
| 9.1.12 | 2 / 3 | |
| 9.1.11 | 2 / 3 | |
| 9.1.10 | 2 / 3 | |
| 9.1.9 | 2 / 3 | |
| 9.1.8 | 2 / 3 | |
| 9.1.7 | 2 / 3 | |
| 9.1.6 | 2 / 3 | |
| 9.1.5 | 2 / 2 | |
| 9.1.4 | 1 / 2 | |
| 9.1.3 | 1 / 2 | |
| 9.1.2 | 1 / 2 | |
| 9.1.1 | 1 / 2 | |
| 9.1.0 | 1 / 2 | |
| 9.0.0 | 1 / 2 |
v9.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.