@fluentui/react-field
Fluent UI Field 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:@griffel/react | AI (dependencies): @griffel/react is the official CSS-in-JS engine for Fluent UI, maintained by Microsoft. Stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): First-party Microsoft Fluent UI dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-label | AI (dependencies): First-party Microsoft Fluent UI dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Microsoft Fluent UI dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Microsoft Fluent UI dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party Microsoft Fluent UI dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party Microsoft Fluent UI dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): First-party Microsoft Fluent UI dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-context-selector | AI (phantom-deps): Same-org scope package declared but not directly imported; benign for this Fluent UI component package. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft OSS package with 1318 days history; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 9.5.2 | 9 / 0 | |
| 9.5.1 | 9 / 0 | |
| 9.5.0 | 9 / 0 | |
| 9.4.16 | 9 / 0 | |
| 9.4.15 | 9 / 0 | |
| 9.4.14 | 9 / 0 | |
| 9.4.13 | 9 / 0 | |
| 9.4.12 | 9 / 5 | |
| 9.4.11 | 9 / 5 | |
| 9.4.10 | 9 / 5 | |
| 9.4.9 | 9 / 5 | |
| 9.4.8 | 9 / 5 | |
| 9.4.7 | 9 / 5 | |
| 9.4.6 | 9 / 5 | |
| 9.4.5 | 9 / 5 | |
| 9.4.4 | 9 / 5 | |
| 9.4.3 | 9 / 5 | |
| 9.4.2 | 9 / 5 | |
| 9.4.1 | 9 / 5 | |
| 9.4.0 | 9 / 5 | |
| 9.3.7 | 9 / 5 | |
| 9.3.6 | 9 / 5 | |
| 9.3.5 | 9 / 5 | |
| 9.3.4 | 9 / 5 | |
| 9.3.3 | 9 / 5 | |
| 9.3.2 | 9 / 5 | |
| 9.3.1 | 9 / 5 | |
| 9.3.0 | 9 / 5 | |
| 9.2.9 | 9 / 5 | |
| 9.2.8 | 9 / 5 | |
| 9.2.7 | 9 / 5 |
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.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.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.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.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 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.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.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.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.