@fluentui/react-progress
Progress component for FluentUI v9
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 Microsoft's CSS-in-JS library, a core dependency of Fluent UI v9. Expected and legitimate for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-field | AI (dependencies): First-party Fluent UI v9 sibling package from the same Microsoft monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Fluent UI v9 sibling package from the same Microsoft monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion | AI (dependencies): First-party Fluent UI v9 sibling package from the same Microsoft monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Fluent UI v9 sibling package from the same Microsoft monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party Fluent UI v9 sibling package from the same Microsoft monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party Fluent UI v9 sibling package from the same Microsoft monorepo. Expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Fluent UI packages predate widespread Sigstore adoption; absence of provenance is consistent across the entire @fluentui/* ecosystem and is not a risk signal here. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 9.5.2 | 8 / 0 | |
| 9.5.1 | 8 / 0 | |
| 9.5.0 | 8 / 0 | |
| 9.4.17 | 8 / 0 | |
| 9.4.16 | 7 / 0 | |
| 9.4.15 | 7 / 0 | |
| 9.4.14 | 7 / 0 | |
| 9.4.13 | 7 / 0 | |
| 9.4.12 | 7 / 4 | |
| 9.4.11 | 7 / 4 | |
| 9.4.10 | 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.7 | 7 / 4 | |
| 9.3.6 | 7 / 4 | |
| 9.3.5 | 7 / 4 | |
| 9.3.4 | 7 / 4 | |
| 9.3.3 | 7 / 4 | |
| 9.3.2 | 7 / 4 | |
| 9.3.1 | 7 / 4 | |
| 9.3.0 | 7 / 4 | |
| 9.2.9 | 7 / 4 | |
| 9.2.8 | 7 / 4 | |
| 9.2.7 | 7 / 4 |
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.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.4.17
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.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.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.4.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.4.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.4.8
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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.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.2.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.