@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, 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 |
|---|---|---|---|---|
| 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 100 of 163)
| Version | Deps | Published |
|---|---|---|
| 9.7.4 | 7 / 0 | |
| 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 | |
| 9.4.6 | 7 / 4 | |
| 9.4.5 | 7 / 4 | |
| 9.4.4 | 7 / 4 | |
| 9.4.3 | 7 / 4 | |
| 9.4.2 | 7 / 4 | |
| 9.4.1 | 7 / 4 | |
| 9.4.0 | 7 / 4 | |
| 9.3.98 | 7 / 4 | |
| 9.3.97 | 7 / 4 | |
| 9.3.96 | 7 / 4 | |
| 9.3.95 | 7 / 4 | |
| 9.3.94 | 7 / 4 | |
| 9.3.93 | 7 / 4 | |
| 9.3.92 | 7 / 4 | |
| 9.3.91 | 7 / 4 | |
| 9.3.90 | 7 / 5 | |
| 9.3.89 | 7 / 5 | |
| 9.3.88 | 7 / 5 | |
| 9.3.87 | 7 / 5 | |
| 9.3.86 | 7 / 5 | |
| 9.3.85 | 7 / 5 | |
| 9.3.84 | 7 / 5 | |
| 9.3.83 | 7 / 5 | |
| 9.3.82 | 7 / 5 | |
| 9.3.81 | 7 / 5 | |
| 9.3.80 | 7 / 5 | |
| 9.3.79 | 7 / 5 | |
| 9.3.78 | 7 / 5 | |
| 9.3.77 | 7 / 5 | |
| 9.3.76 | 7 / 5 | |
| 9.3.75 | 7 / 5 | |
| 9.3.74 | 7 / 5 | |
| 9.3.73 | 7 / 5 | |
| 9.3.72 | 7 / 5 | |
| 9.3.71 | 7 / 5 | |
| 9.3.70 | 7 / 5 | |
| 9.3.69 | 7 / 5 | |
| 9.3.68 | 7 / 5 | |
| 9.3.67 | 7 / 5 | |
| 9.3.66 | 7 / 5 | |
| 9.3.65 | 7 / 5 | |
| 9.3.64 | 7 / 5 | |
| 9.3.63 | 7 / 5 | |
| 9.3.62 | 7 / 5 | |
| 9.3.61 | 7 / 5 | |
| 9.3.60 | 7 / 5 | |
| 9.3.59 | 7 / 5 | |
| 9.3.58 | 7 / 5 | |
| 9.3.57 | 7 / 5 | |
| 9.3.56 | 7 / 5 | |
| 9.3.55 | 7 / 5 | |
| 9.3.54 | 7 / 5 | |
| 9.3.53 | 7 / 5 | |
| 9.3.52 | 7 / 5 | |
| 9.3.51 | 7 / 5 | |
| 9.3.50 | 7 / 5 | |
| 9.3.49 | 7 / 5 | |
| 9.3.48 | 7 / 5 | |
| 9.3.47 | 7 / 5 | |
| 9.3.46 | 7 / 5 | |
| 9.3.45 | 7 / 5 | |
| 9.3.44 | 7 / 5 | |
| 9.3.43 | 7 / 5 | |
| 9.3.42 | 7 / 5 | |
| 9.3.41 | 7 / 5 | |
| 9.3.39 | 7 / 5 | |
| 9.3.38 | 7 / 5 |
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.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.73
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.72
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.71
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.70
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.69
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.68
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.67
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.66
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.65
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.64
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.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.