@fluentui/react-positioning
A react wrapper around Popper.js for Fluent UI
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:floating-ui-devtools | AI (dependencies): Devtools helper dep from trusted FluentUI publisher; no malicious behavior indicated. | ai | |
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is a Microsoft-maintained CSS-in-JS library for Fluent UI; a stable, legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:@floating-ui/devtools | AI (dependencies): @floating-ui/devtools is part of the well-known floating-ui library; legitimate dependency for a positioning utility package. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft Fluent UI monorepo packages published by uifabricteam do not use Sigstore provenance; this is a stable characteristic of the package family, not a risk indicator. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): Internal Fluent UI monorepo package maintained by Microsoft; stable legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): Internal Fluent UI monorepo package maintained by Microsoft; stable legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): Internal Fluent UI monorepo package maintained by Microsoft; stable legitimate dependency. | ai |
Versions (showing 46 of 146)
| Version | Deps | Published |
|---|---|---|
| 9.9.0 | 6 / 3 | |
| 9.8.0 | 6 / 3 | |
| 9.7.3 | 6 / 3 | |
| 9.7.2 | 6 / 3 | |
| 9.7.1 | 6 / 3 | |
| 9.7.0 | 6 / 3 | |
| 9.6.0 | 6 / 3 | |
| 9.5.14 | 6 / 3 | |
| 9.5.13 | 6 / 3 | |
| 9.5.12 | 6 / 3 | |
| 9.5.11 | 6 / 3 | |
| 9.5.10 | 6 / 3 | |
| 9.5.9 | 6 / 3 | |
| 9.5.8 | 6 / 3 | |
| 9.5.7 | 6 / 3 | |
| 9.5.6 | 6 / 3 | |
| 9.5.5 | 6 / 3 | |
| 9.5.4 | 6 / 3 | |
| 9.5.3 | 6 / 3 | |
| 9.5.2 | 6 / 3 | |
| 9.5.1 | 6 / 3 | |
| 9.5.0 | 6 / 3 | |
| 9.4.3 | 6 / 3 | |
| 9.4.2 | 6 / 3 | |
| 9.4.1 | 6 / 3 | |
| 9.4.0 | 6 / 3 | |
| 9.3.11 | 6 / 3 | |
| 9.3.10 | 6 / 3 | |
| 9.3.9 | 6 / 3 | |
| 9.3.8 | 6 / 3 | |
| 9.3.7 | 6 / 2 | |
| 9.3.6 | 6 / 2 | |
| 9.3.5 | 6 / 2 | |
| 9.3.4 | 6 / 2 | |
| 9.3.3 | 6 / 2 | |
| 9.3.2 | 6 / 2 | |
| 9.3.1 | 6 / 2 | |
| 9.3.0 | 6 / 2 | |
| 9.2.2 | 6 / 2 | |
| 9.2.1 | 6 / 2 | |
| 9.2.0 | 6 / 2 | |
| 9.1.2 | 6 / 2 | |
| 9.1.1 | 6 / 2 | |
| 9.1.0 | 6 / 2 | |
| 9.0.1 | 6 / 2 | |
| 9.0.0 | 6 / 2 |
v9.9.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.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.3
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.2
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.1
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.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.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.14
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.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.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.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.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.5.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.5.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.5.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.5.3
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.2
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.1
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.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.3
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.2
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.1
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.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.3.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.3.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.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.
v9.3.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.3.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.3.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.3.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.3.3
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.2
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.1
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.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.2.2
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.1
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.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.1.2
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.1
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.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.0.1
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.0.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.