@fluentui/react-spinner
Spinner component for Fluent UI React
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 is Microsoft's official CSS-in-JS library, a known legitimate dependency for all Fluent UI v9 components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-label | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package with 1464-day history and 1098 versions; lack of Sigstore provenance is a low risk for this well-known publisher. | ai |
Versions (showing 24 of 24)
| 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.15 | 7 / 0 | |
| 9.7.14 | 7 / 0 | |
| 9.7.13 | 7 / 0 | |
| 9.7.12 | 7 / 4 | |
| 9.7.11 | 7 / 4 | |
| 9.7.10 | 7 / 4 | |
| 9.7.9 | 7 / 4 | |
| 9.7.8 | 7 / 4 | |
| 9.7.7 | 7 / 4 | |
| 9.7.6 | 7 / 4 | |
| 9.7.5 | 7 / 4 | |
| 9.7.4 | 7 / 4 | |
| 9.7.3 | 7 / 4 | |
| 9.7.2 | 7 / 4 | |
| 9.7.1 | 7 / 4 | |
| 9.7.0 | 7 / 4 | |
| 9.6.2 | 7 / 4 | |
| 9.6.1 | 7 / 4 | |
| 9.6.0 | 7 / 4 | |
| 9.5.12 | 7 / 4 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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.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.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.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.