@fluentui/react-slider
Fluent UI React Slider 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. It is a legitimate and expected dependency for all @fluentui/* components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-field | AI (dependencies): First-party @fluentui/* sibling package from Microsoft's Fluent UI monorepo. Expected dependency, not a risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party @fluentui/* sibling package from Microsoft's Fluent UI monorepo. Expected dependency, not a risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party @fluentui/* sibling package from Microsoft's Fluent UI monorepo. Expected dependency, not a risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party @fluentui/* sibling package from Microsoft's Fluent UI monorepo. Expected dependency, not a risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party @fluentui/* sibling package from Microsoft's Fluent UI monorepo. Expected dependency, not a risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui/* sibling package from Microsoft's Fluent UI monorepo. Expected dependency, not a risk. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package published via uifabricteam. Lack of Sigstore provenance is common and not a risk signal for this well-known package family. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 9.6.3 | 8 / 0 | |
| 9.6.2 | 8 / 0 | |
| 9.6.1 | 8 / 0 | |
| 9.6.0 | 8 / 0 | |
| 9.5.16 | 8 / 0 | |
| 9.5.15 | 8 / 0 | |
| 9.5.14 | 8 / 0 | |
| 9.5.13 | 8 / 0 | |
| 9.5.12 | 8 / 5 | |
| 9.5.11 | 8 / 5 | |
| 9.5.10 | 8 / 5 | |
| 9.5.9 | 8 / 5 | |
| 9.5.8 | 8 / 5 | |
| 9.5.7 | 8 / 5 | |
| 9.5.6 | 8 / 5 | |
| 9.5.5 | 8 / 5 | |
| 9.5.4 | 8 / 5 | |
| 9.5.3 | 8 / 5 | |
| 9.5.2 | 8 / 5 | |
| 9.5.1 | 8 / 5 | |
| 9.5.0 | 8 / 5 | |
| 9.4.7 | 8 / 5 | |
| 9.4.6 | 8 / 5 | |
| 9.4.5 | 8 / 5 | |
| 9.4.4 | 8 / 5 | |
| 9.4.3 | 8 / 5 | |
| 9.4.2 | 8 / 5 | |
| 9.4.1 | 8 / 5 | |
| 9.4.0 | 8 / 5 | |
| 9.3.10 | 8 / 5 | |
| 9.3.9 | 8 / 5 | |
| 9.3.8 | 8 / 5 |
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.11
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.10
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.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. 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.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.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.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.3.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.