@fluentui/react-divider MIT 34 versions

@fluentui/react-divider

npm Repository Homepage

Fluent UI component to visually separate content.

34

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

chrisdholtmiroslavstastnylevithomasonuifabricteamuifrnbotlayershifterjustslonemicrosoft1essopranopillow

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:lib/components/Divider/useDividerStyles.styles.js	AI (source-diff): Griffel-compiled style atoms produce long lines; not obfuscation, stable for this package.	ai	2026/07/21
dependencies	unvetted-dep:@griffel/react	AI (dependencies): Griffel is Microsoft's CSS-in-JS library, a core dependency of the Fluent UI v9 ecosystem. Stable and expected.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-theme	AI (dependencies): First-party Fluent UI monorepo package from Microsoft; expected dependency for this component.	ai	2026/04/25
provenance	no-provenance	AI (provenance): Long-established Microsoft Fluent UI package; lack of Sigstore provenance is expected for packages of this age and is not a risk signal.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-jsx-runtime	AI (dependencies): First-party Fluent UI monorepo package from Microsoft; expected dependency for this component.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-shared-contexts	AI (dependencies): First-party Fluent UI monorepo package from Microsoft; expected dependency for this component.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-utilities	AI (dependencies): First-party Fluent UI monorepo package from Microsoft; expected dependency for this component.	ai	2026/04/25

Versions (showing 34 of 134)

Version	Deps	Published
9.2.10	6 / 5	2023-04-24
9.2.9	5 / 5	2023-04-17
9.2.8	5 / 5	2023-04-12
9.2.7	5 / 5	2023-04-04
9.2.6	5 / 5	2023-03-23
9.2.5	5 / 5	2023-03-21
9.2.4	5 / 5	2023-03-16
9.2.3	5 / 5	2023-03-15
9.2.2	5 / 5	2023-03-13
9.2.1	5 / 5	2023-03-10
9.2.0	5 / 5	2023-03-08
9.1.16	4 / 5	2023-02-15
9.1.15	4 / 5	2023-02-13
9.1.14	4 / 5	2023-02-10
9.1.13	4 / 5	2023-01-31
9.1.12	4 / 5	2023-01-26
9.1.11	4 / 5	2023-01-16
9.1.10	4 / 4	2023-01-09
9.1.9	4 / 4	2023-01-04
9.1.8	4 / 4	2022-12-21
9.1.7	4 / 4	2022-12-20
9.1.6	4 / 4	2022-12-05
9.1.5	4 / 4	2022-11-17
9.1.4	4 / 4	2022-11-11
9.1.3	4 / 4	2022-11-02
9.1.2	4 / 4	2022-10-20
9.1.1	4 / 4	2022-10-13
9.1.0	4 / 4	2022-09-20
9.0.5	4 / 4	2022-09-15
9.0.4	4 / 4	2022-08-03
9.0.3	4 / 4	2022-07-14
9.0.2	4 / 4	2022-07-14
9.0.1	4 / 4	2022-06-28
9.0.0	4 / 4	2022-06-28

v9.2.10

1 finding

INFO No provenance attestation provenance

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

v9.2.9

1 finding

INFO No provenance attestation provenance

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

v9.2.8

1 finding

INFO No provenance attestation provenance

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

v9.2.7

1 finding

INFO No provenance attestation provenance

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

v9.2.6

1 finding

INFO No provenance attestation provenance

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

v9.2.5

1 finding

INFO No provenance attestation provenance

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

v9.2.4

1 finding

INFO No provenance attestation provenance

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

v9.2.3

1 finding

INFO No provenance attestation provenance

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

v9.2.2

1 finding

INFO No provenance attestation provenance

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

v9.2.1

1 finding

INFO No provenance attestation provenance

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

v9.2.0

1 finding

INFO No provenance attestation provenance

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

v9.1.16

1 finding

INFO No provenance attestation provenance

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

v9.1.15

1 finding

INFO No provenance attestation provenance

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

v9.1.14

1 finding

INFO No provenance attestation provenance

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

v9.1.13

1 finding

INFO No provenance attestation provenance

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

v9.1.12

1 finding

INFO No provenance attestation provenance

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

v9.1.11

1 finding

INFO No provenance attestation provenance

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

v9.1.10

1 finding

INFO No provenance attestation provenance

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

v9.1.9

1 finding

INFO No provenance attestation provenance

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

v9.1.8

1 finding

INFO No provenance attestation provenance

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

v9.1.7

1 finding

INFO No provenance attestation provenance

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

v9.1.6

1 finding

INFO No provenance attestation provenance

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

v9.1.5

1 finding

INFO No provenance attestation provenance

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

v9.1.4

1 finding

INFO No provenance attestation provenance

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

v9.1.3

1 finding

INFO No provenance attestation provenance

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

v9.1.2

1 finding

INFO No provenance attestation provenance

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

v9.1.1

1 finding

INFO No provenance attestation provenance

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

v9.1.0

1 finding

INFO No provenance attestation provenance

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

v9.0.5

1 finding

INFO No provenance attestation provenance

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

v9.0.4

1 finding

INFO No provenance attestation provenance

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

v9.0.3

1 finding

INFO No provenance attestation provenance

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

v9.0.2

1 finding

INFO No provenance attestation provenance

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

v9.0.1

1 finding

INFO No provenance attestation provenance

[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

INFO No provenance attestation provenance

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