@fluentui/react-migration-v8-v9
Migration shim components and methods for hybrid v8/v9 applications building on 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance adoption is ~12% industry-wide; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@fluentui/react | AI (dependencies): Same Microsoft @fluentui org; dependency is expected and stable for this migration shim package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-hooks | AI (dependencies): Same Microsoft @fluentui org; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/fluent2-theme | AI (dependencies): Same Microsoft @fluentui org; expected dependency for this package. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-icons | AI (phantom-deps): Same-org dep listed in package.json dependencies; phantom-dep heuristic false positive for this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Migration shim library from Microsoft's FluentUI monorepo; sparse README is expected for internal tooling packages. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 9.10.12 | 8 / 0 | |
| 9.10.11 | 8 / 0 | |
| 9.10.9 | 8 / 0 | |
| 9.10.8 | 8 / 0 | |
| 9.10.7 | 8 / 0 | |
| 9.10.6 | 8 / 0 | |
| 9.10.5 | 8 / 0 | |
| 9.10.4 | 8 / 0 | |
| 9.10.3 | 8 / 0 | |
| 9.10.2 | 8 / 0 | |
| 9.10.1 | 8 / 0 | |
| 9.10.0 | 8 / 0 | |
| 9.9.18 | 8 / 4 | |
| 9.9.17 | 8 / 4 | |
| 9.9.16 | 8 / 4 | |
| 9.9.15 | 8 / 4 | |
| 9.9.14 | 8 / 4 | |
| 9.9.13 | 8 / 4 | |
| 9.9.12 | 8 / 4 | |
| 9.9.11 | 8 / 4 | |
| 9.9.10 | 8 / 4 | |
| 9.9.9 | 8 / 4 | |
| 9.9.8 | 8 / 4 | |
| 9.9.7 | 8 / 4 | |
| 9.9.6 | 8 / 4 | |
| 9.9.5 | 8 / 4 | |
| 9.9.4 | 8 / 4 | |
| 9.9.3 | 8 / 4 | |
| 9.9.2 | 8 / 4 | |
| 9.9.1 | 8 / 4 | |
| 9.9.0 | 8 / 4 | |
| 9.8.8 | 8 / 4 | |
| 9.8.7 | 8 / 4 | |
| 9.8.6 | 8 / 4 | |
| 9.8.5 | 8 / 4 | |
| 9.8.4 | 8 / 4 | |
| 9.8.3 | 8 / 4 | |
| 9.8.2 | 8 / 4 | |
| 9.8.1 | 8 / 4 | |
| 9.8.0 | 8 / 4 | |
| 9.7.13 | 8 / 4 | |
| 9.7.12 | 8 / 4 | |
| 9.7.11 | 8 / 4 |
v9.10.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.13
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.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.7.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.