@fluentui/react-label
Fluent UI React Label component
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Microsoft's Fluent UI monorepo packages do not currently publish Sigstore provenance; this is consistent across all versions and not a risk indicator for this well-established package. | ai | |
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): Griffel is the official CSS-in-JS library for Fluent UI v9, maintained by the same Microsoft team. Expected and legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Fluent UI sibling package from the Microsoft monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Fluent UI sibling package from the Microsoft monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party Fluent UI sibling package from the Microsoft monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party Fluent UI sibling package from the Microsoft monorepo. Expected dependency. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 9.4.2 | 6 / 0 | |
| 9.4.1 | 6 / 0 | |
| 9.4.0 | 6 / 0 | |
| 9.3.15 | 6 / 0 | |
| 9.3.14 | 6 / 0 | |
| 9.3.13 | 6 / 0 | |
| 9.3.12 | 6 / 4 | |
| 9.3.11 | 6 / 4 | |
| 9.3.10 | 6 / 4 | |
| 9.3.9 | 6 / 4 | |
| 9.3.8 | 6 / 4 | |
| 9.3.7 | 6 / 4 | |
| 9.3.6 | 6 / 4 | |
| 9.3.5 | 6 / 4 | |
| 9.3.4 | 6 / 4 | |
| 9.3.3 | 6 / 4 | |
| 9.3.2 | 6 / 4 | |
| 9.3.1 | 6 / 4 | |
| 9.3.0 | 6 / 4 | |
| 9.2.2 | 6 / 4 | |
| 9.2.1 | 6 / 4 | |
| 9.2.0 | 6 / 4 | |
| 9.1.88 | 6 / 4 |
v9.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.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.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.11
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.3.10
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.3.9
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.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.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.2.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.1.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.