@fluentui/react-textarea
Fluent UI TextArea 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): Established Microsoft Fluent UI package published by uifabricteam; lack of Sigstore provenance is expected for this publisher and not a meaningful risk signal. | ai | |
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is Microsoft's CSS-in-JS library built specifically for Fluent UI; it is a trusted first-party dependency in this ecosystem. | ai | |
| dependencies | unvetted-dep:@fluentui/react-field | AI (dependencies): First-party @fluentui/* package from the same Microsoft monorepo; no risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party @fluentui/* package from the same Microsoft monorepo; no risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party @fluentui/* package from the same Microsoft monorepo; no risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party @fluentui/* package from the same Microsoft monorepo; no risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui/* package from the same Microsoft monorepo; no risk. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 9.7.3 | 7 / 0 | |
| 9.7.2 | 7 / 0 | |
| 9.7.1 | 7 / 0 | |
| 9.7.0 | 7 / 0 | |
| 9.6.16 | 7 / 0 | |
| 9.6.15 | 7 / 0 | |
| 9.6.14 | 7 / 0 | |
| 9.6.13 | 7 / 0 | |
| 9.6.12 | 7 / 4 | |
| 9.6.11 | 7 / 4 | |
| 9.6.10 | 7 / 4 | |
| 9.6.9 | 7 / 4 | |
| 9.6.8 | 7 / 4 | |
| 9.6.7 | 7 / 4 | |
| 9.6.6 | 7 / 4 | |
| 9.6.5 | 7 / 4 | |
| 9.6.4 | 7 / 4 | |
| 9.6.3 | 7 / 4 | |
| 9.6.2 | 7 / 4 | |
| 9.6.1 | 7 / 4 | |
| 9.6.0 | 7 / 4 | |
| 9.5.7 | 7 / 4 | |
| 9.5.6 | 7 / 4 | |
| 9.5.5 | 7 / 4 | |
| 9.5.4 | 7 / 4 | |
| 9.5.3 | 7 / 4 | |
| 9.5.2 | 7 / 4 | |
| 9.5.1 | 7 / 4 | |
| 9.5.0 | 7 / 4 | |
| 9.4.9 | 7 / 4 | |
| 9.4.8 | 7 / 4 | |
| 9.4.7 | 7 / 4 |
v9.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.7.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.7.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.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.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.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.4
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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.4
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.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.8
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.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.