@fluentui/react-overflow
React bindings for @fluentui/priority-overflow
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:@griffel/react | AI (dependencies): Griffel is Microsoft's official CSS-in-JS library, a legitimate first-party dependency of Fluent UI packages. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Fluent UI package from the same Microsoft monorepo; not a security concern. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Fluent UI package from the same Microsoft monorepo; not a security concern. | ai | |
| dependencies | unvetted-dep:@fluentui/priority-overflow | AI (dependencies): First-party Fluent UI package from the same Microsoft monorepo; not a security concern. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): First-party Fluent UI package from the same Microsoft monorepo; not a security concern. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-theme | AI (phantom-deps): Common pattern in large monorepos; @fluentui/react-theme may be used for types/tokens without a direct import. Not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Large monorepo component packages routinely have minimal standalone READMEs; not indicative of spam or malice for Fluent UI. | ai |
Versions (showing 25 of 125)
| Version | Deps | Published |
|---|---|---|
| 9.0.24 | 6 / 4 | |
| 9.0.23 | 6 / 4 | |
| 9.0.22 | 6 / 4 | |
| 9.0.21 | 6 / 4 | |
| 9.0.20 | 6 / 4 | |
| 9.0.19 | 6 / 4 | |
| 9.0.18 | 6 / 4 | |
| 9.0.17 | 6 / 4 | |
| 9.0.16 | 6 / 4 | |
| 9.0.15 | 6 / 4 | |
| 9.0.14 | 6 / 4 | |
| 9.0.13 | 6 / 4 | |
| 9.0.12 | 6 / 4 | |
| 9.0.11 | 6 / 4 | |
| 9.0.10 | 6 / 4 | |
| 9.0.9 | 6 / 4 | |
| 9.0.8 | 6 / 4 | |
| 9.0.7 | 6 / 4 | |
| 9.0.6 | 6 / 4 | |
| 9.0.5 | 6 / 4 | |
| 9.0.4 | 6 / 4 | |
| 9.0.3 | 6 / 4 | |
| 9.0.2 | 6 / 4 | |
| 9.0.1 | 6 / 4 | |
| 9.0.0 | 6 / 4 |
v9.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.