@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, 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:@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 100 of 126)
| Version | Deps | Published |
|---|---|---|
| 9.5.3 | 9 / 0 | |
| 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 | |
| 9.2.6 | 9 / 5 | |
| 9.2.5 | 9 / 5 | |
| 9.2.4 | 9 / 5 | |
| 9.2.3 | 9 / 5 | |
| 9.2.2 | 8 / 5 | |
| 9.2.1 | 8 / 5 | |
| 9.2.0 | 8 / 5 | |
| 9.1.86 | 8 / 5 | |
| 9.1.85 | 8 / 5 | |
| 9.1.84 | 8 / 5 | |
| 9.1.83 | 8 / 5 | |
| 9.1.82 | 8 / 5 | |
| 9.1.81 | 8 / 5 | |
| 9.1.80 | 8 / 5 | |
| 9.1.79 | 8 / 5 | |
| 9.1.78 | 8 / 6 | |
| 9.1.77 | 8 / 6 | |
| 9.1.76 | 8 / 6 | |
| 9.1.75 | 8 / 6 | |
| 9.1.74 | 8 / 6 | |
| 9.1.73 | 8 / 6 | |
| 9.1.72 | 8 / 6 | |
| 9.1.71 | 8 / 6 | |
| 9.1.70 | 8 / 6 | |
| 9.1.69 | 8 / 6 | |
| 9.1.68 | 8 / 6 | |
| 9.1.67 | 8 / 5 | |
| 9.1.66 | 8 / 5 | |
| 9.1.65 | 8 / 5 | |
| 9.1.64 | 8 / 5 | |
| 9.1.63 | 8 / 5 | |
| 9.1.62 | 8 / 5 | |
| 9.1.61 | 8 / 5 | |
| 9.1.60 | 8 / 5 | |
| 9.1.59 | 8 / 5 | |
| 9.1.58 | 8 / 5 | |
| 9.1.57 | 8 / 5 | |
| 9.1.56 | 8 / 5 | |
| 9.1.55 | 8 / 5 | |
| 9.1.54 | 8 / 5 | |
| 9.1.53 | 8 / 5 | |
| 9.1.52 | 8 / 5 | |
| 9.1.51 | 8 / 5 | |
| 9.1.50 | 8 / 5 | |
| 9.1.49 | 8 / 5 | |
| 9.1.48 | 8 / 5 | |
| 9.1.47 | 8 / 5 | |
| 9.1.46 | 8 / 5 | |
| 9.1.45 | 8 / 5 | |
| 9.1.44 | 8 / 5 | |
| 9.1.43 | 8 / 5 | |
| 9.1.42 | 8 / 5 | |
| 9.1.41 | 8 / 5 | |
| 9.1.40 | 8 / 5 | |
| 9.1.39 | 8 / 5 | |
| 9.1.38 | 8 / 5 | |
| 9.1.37 | 8 / 5 | |
| 9.1.36 | 8 / 5 | |
| 9.1.35 | 8 / 5 | |
| 9.1.34 | 8 / 5 | |
| 9.1.33 | 8 / 5 | |
| 9.1.32 | 8 / 5 | |
| 9.1.31 | 8 / 5 | |
| 9.1.30 | 8 / 5 | |
| 9.1.29 | 8 / 5 | |
| 9.1.28 | 8 / 5 | |
| 9.1.27 | 8 / 5 | |
| 9.1.26 | 8 / 5 |
v9.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.3
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. 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.
v9.1.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.63
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.62
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.61
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.60
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.59
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.58
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.57
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.56
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.55
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.54
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.53
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.52
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.51
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.50
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.49
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.48
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.47
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.46
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.45
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.44
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.43
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.42
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.41
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.40
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.39
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.38
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.37
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.36
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.35
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.34
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.33
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.32
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.31
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.30
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.29
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.28
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.27
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.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.