@fluentui/react-input
Fluent UI React Input 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is the official CSS-in-JS engine for Fluent UI, maintained by Microsoft; a stable, legitimate dependency for all @fluentui/* packages. | ai | |
| dependencies | unvetted-dep:@fluentui/react-field | AI (dependencies): First-party @fluentui/* sibling package from Microsoft; legitimate and expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party @fluentui/* sibling package from Microsoft; legitimate and expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party @fluentui/* sibling package from Microsoft; legitimate and expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party @fluentui/* sibling package from Microsoft; legitimate and expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui/* sibling package from Microsoft; legitimate and expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft's Fluent UI packages do not currently publish Sigstore provenance; consistent across all versions, not a risk indicator for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 9.8.3 | 7 / 0 | |
| 9.8.2 | 7 / 0 | |
| 9.8.1 | 7 / 0 | |
| 9.8.0 | 7 / 0 | |
| 9.7.16 | 7 / 0 | |
| 9.7.15 | 7 / 0 | |
| 9.7.14 | 7 / 0 | |
| 9.7.13 | 7 / 0 | |
| 9.7.12 | 7 / 5 | |
| 9.7.11 | 7 / 5 | |
| 9.7.10 | 7 / 5 | |
| 9.7.9 | 7 / 5 | |
| 9.7.8 | 7 / 5 | |
| 9.7.7 | 7 / 5 | |
| 9.7.6 | 7 / 5 | |
| 9.7.5 | 7 / 5 | |
| 9.7.4 | 7 / 5 | |
| 9.7.3 | 7 / 5 | |
| 9.7.2 | 7 / 5 | |
| 9.7.1 | 7 / 5 | |
| 9.7.0 | 7 / 5 | |
| 9.6.7 | 7 / 5 | |
| 9.6.6 | 7 / 5 | |
| 9.6.5 | 7 / 5 | |
| 9.6.4 | 7 / 5 | |
| 9.6.3 | 7 / 5 | |
| 9.6.2 | 7 / 5 | |
| 9.6.1 | 7 / 5 | |
| 9.6.0 | 7 / 5 | |
| 9.5.9 | 7 / 5 | |
| 9.5.8 | 7 / 5 | |
| 9.5.7 | 7 / 5 |
v9.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.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.8.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.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.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.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
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.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.5.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.5.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.