@fluentui/react-list
React List 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:@fluentui/react-theme | AI (dependencies): Core Fluent UI v9 monorepo package from Microsoft; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is the official CSS-in-JS library for Fluent UI v9, maintained by Microsoft. A stable, expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): Core Fluent UI v9 monorepo package from Microsoft; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): Core Fluent UI v9 monorepo package from Microsoft; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-checkbox | AI (dependencies): Core Fluent UI v9 monorepo package from Microsoft; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): Core Fluent UI v9 monorepo package from Microsoft; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): Core Fluent UI v9 monorepo package from Microsoft; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): Core Fluent UI v9 monorepo package from Microsoft; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): Core Fluent UI v9 monorepo package from Microsoft; expected dependency for this component. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Fluent UI component packages in the monorepo commonly lack keywords and have minimal READMEs; not indicative of spam or malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft's Fluent UI monorepo does not currently publish with Sigstore provenance; this is consistent across all versions and not a security concern. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 9.6.15 | 10 / 0 | |
| 9.6.14 | 10 / 0 | |
| 9.6.13 | 10 / 0 | |
| 9.6.12 | 10 / 0 | |
| 9.6.11 | 10 / 0 | |
| 9.6.10 | 10 / 0 | |
| 9.6.9 | 10 / 0 | |
| 9.6.8 | 10 / 0 | |
| 9.6.7 | 10 / 6 | |
| 9.6.6 | 10 / 6 | |
| 9.6.5 | 10 / 6 | |
| 9.6.4 | 10 / 6 | |
| 9.6.3 | 10 / 6 | |
| 9.6.2 | 10 / 6 | |
| 9.6.1 | 10 / 6 | |
| 9.6.0 | 10 / 6 | |
| 9.5.0 | 10 / 6 | |
| 9.4.2 | 10 / 6 | |
| 9.4.1 | 10 / 6 | |
| 9.4.0 | 10 / 6 | |
| 9.3.0 | 10 / 6 | |
| 9.2.7 | 10 / 6 | |
| 9.2.6 | 10 / 6 | |
| 9.2.5 | 10 / 6 | |
| 9.2.4 | 10 / 6 | |
| 9.2.3 | 10 / 6 | |
| 9.2.2 | 10 / 6 | |
| 9.2.1 | 10 / 6 | |
| 9.2.0 | 10 / 6 | |
| 9.1.9 | 10 / 6 | |
| 9.1.8 | 10 / 6 | |
| 9.1.7 | 10 / 6 |
v9.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.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.
v9.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.8
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.6.6
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.6.5
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.6.4
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.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.0
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.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.1.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.