@fluentui/react-overflow MIT 30 versions

@fluentui/react-overflow

npm Repository Homepage

React bindings for @fluentui/priority-overflow

30

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

chrisdholtmiroslavstastnylevithomasonuifabricteamuifrnbotlayershifterjustslonemicrosoft1essopranopillow

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	2026/04/25
dependencies	unvetted-dep:@fluentui/react-theme	AI (dependencies): First-party Fluent UI package from the same Microsoft monorepo; not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-utilities	AI (dependencies): First-party Fluent UI package from the same Microsoft monorepo; not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/priority-overflow	AI (dependencies): First-party Fluent UI package from the same Microsoft monorepo; not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-context-selector	AI (dependencies): First-party Fluent UI package from the same Microsoft monorepo; not a security concern.	ai	2026/04/25
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	2026/04/25
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	2026/04/25

Versions (showing 30 of 30)

Version	Deps	Published
9.8.0	7 / 0	2026-05-26
9.7.2	6 / 0	2026-04-23
9.7.1	6 / 0	2026-02-25
9.7.0	6 / 0	2026-02-12
9.6.7	6 / 0	2026-01-22
9.6.6	6 / 5	2025-12-17
9.6.5	6 / 5	2025-11-11
9.6.4	6 / 5	2025-11-06
9.6.3	6 / 5	2025-10-31
9.6.2	6 / 5	2025-10-21
9.6.1	6 / 5	2025-10-08
9.6.0	6 / 5	2025-10-02
9.5.6	6 / 5	2025-09-08
9.5.5	6 / 5	2025-08-21
9.5.4	6 / 5	2025-08-07
9.5.3	6 / 5	2025-07-30
9.5.2	6 / 5	2025-07-30
9.5.1	6 / 5	2025-07-28
9.5.0	6 / 5	2025-07-17
9.4.7	6 / 5	2025-07-11
9.4.6	6 / 5	2025-07-04
9.4.5	6 / 5	2025-06-27
9.4.4	6 / 5	2025-06-26
9.4.3	6 / 5	2025-06-23
9.4.2	6 / 5	2025-06-18
9.4.1	6 / 5	2025-06-13
9.4.0	6 / 5	2025-06-12
9.3.9	6 / 5	2025-06-11
9.3.8	6 / 5	2025-06-06
9.3.7	6 / 5	2025-05-14

v9.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.7.2

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.6.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.6.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.6.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.6.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.6.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.