@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 100 of 125)
| Version | Deps | Published |
|---|---|---|
| 9.9.1 | 6 / 0 | |
| 9.9.0 | 6 / 0 | |
| 9.8.0 | 7 / 0 | |
| 9.7.2 | 6 / 0 | |
| 9.7.1 | 6 / 0 | |
| 9.7.0 | 6 / 0 | |
| 9.6.7 | 6 / 0 | |
| 9.6.6 | 6 / 5 | |
| 9.6.5 | 6 / 5 | |
| 9.6.4 | 6 / 5 | |
| 9.6.3 | 6 / 5 | |
| 9.6.2 | 6 / 5 | |
| 9.6.1 | 6 / 5 | |
| 9.6.0 | 6 / 5 | |
| 9.5.6 | 6 / 5 | |
| 9.5.5 | 6 / 5 | |
| 9.5.4 | 6 / 5 | |
| 9.5.3 | 6 / 5 | |
| 9.5.2 | 6 / 5 | |
| 9.5.1 | 6 / 5 | |
| 9.5.0 | 6 / 5 | |
| 9.4.7 | 6 / 5 | |
| 9.4.6 | 6 / 5 | |
| 9.4.5 | 6 / 5 | |
| 9.4.4 | 6 / 5 | |
| 9.4.3 | 6 / 5 | |
| 9.4.2 | 6 / 5 | |
| 9.4.1 | 6 / 5 | |
| 9.4.0 | 6 / 5 | |
| 9.3.9 | 6 / 5 | |
| 9.3.8 | 6 / 5 | |
| 9.3.7 | 6 / 5 | |
| 9.3.6 | 6 / 5 | |
| 9.3.5 | 6 / 5 | |
| 9.3.4 | 6 / 5 | |
| 9.3.3 | 6 / 5 | |
| 9.3.2 | 6 / 5 | |
| 9.3.1 | 6 / 5 | |
| 9.3.0 | 6 / 5 | |
| 9.2.8 | 6 / 5 | |
| 9.2.7 | 6 / 5 | |
| 9.2.6 | 6 / 5 | |
| 9.2.5 | 6 / 5 | |
| 9.2.4 | 6 / 5 | |
| 9.2.3 | 6 / 5 | |
| 9.2.2 | 6 / 5 | |
| 9.2.1 | 6 / 5 | |
| 9.2.0 | 6 / 5 | |
| 9.1.32 | 6 / 6 | |
| 9.1.31 | 6 / 6 | |
| 9.1.30 | 6 / 6 | |
| 9.1.29 | 6 / 6 | |
| 9.1.28 | 6 / 6 | |
| 9.1.27 | 6 / 6 | |
| 9.1.26 | 6 / 6 | |
| 9.1.25 | 6 / 6 | |
| 9.1.24 | 6 / 6 | |
| 9.1.23 | 6 / 6 | |
| 9.1.22 | 6 / 6 | |
| 9.1.21 | 6 / 6 | |
| 9.1.20 | 6 / 4 | |
| 9.1.19 | 6 / 4 | |
| 9.1.18 | 6 / 4 | |
| 9.1.17 | 6 / 4 | |
| 9.1.16 | 6 / 4 | |
| 9.1.15 | 6 / 4 | |
| 9.1.14 | 6 / 4 | |
| 9.1.13 | 6 / 4 | |
| 9.1.12 | 6 / 4 | |
| 9.1.11 | 6 / 4 | |
| 9.1.10 | 6 / 4 | |
| 9.1.9 | 6 / 4 | |
| 9.1.8 | 6 / 4 | |
| 9.1.7 | 6 / 4 | |
| 9.1.6 | 6 / 4 | |
| 9.1.5 | 6 / 4 | |
| 9.1.4 | 6 / 4 | |
| 9.1.3 | 6 / 4 | |
| 9.1.2 | 6 / 4 | |
| 9.1.1 | 6 / 4 | |
| 9.1.0 | 6 / 4 | |
| 9.0.43 | 6 / 4 | |
| 9.0.42 | 6 / 4 | |
| 9.0.41 | 6 / 4 | |
| 9.0.40 | 6 / 4 | |
| 9.0.39 | 6 / 4 | |
| 9.0.38 | 6 / 4 | |
| 9.0.37 | 6 / 4 | |
| 9.0.36 | 6 / 4 | |
| 9.0.35 | 6 / 4 | |
| 9.0.34 | 6 / 4 | |
| 9.0.33 | 6 / 4 | |
| 9.0.32 | 6 / 4 | |
| 9.0.31 | 6 / 4 | |
| 9.0.30 | 6 / 4 | |
| 9.0.29 | 6 / 4 | |
| 9.0.28 | 6 / 4 | |
| 9.0.27 | 6 / 4 | |
| 9.0.26 | 6 / 4 | |
| 9.0.25 | 6 / 4 |
v9.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.