@fluentui/react-breadcrumb MIT 32 versions

@fluentui/react-breadcrumb

npm Repository Homepage

Breadcrumb component for Fluent UI React.

32

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/react is the Microsoft-maintained CSS-in-JS engine for Fluent UI; a legitimate first-party dependency for all @fluentui/* packages.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-aria	AI (dependencies): First-party @fluentui sibling package from Microsoft's monorepo; no security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-link	AI (dependencies): First-party @fluentui sibling package from Microsoft's monorepo; no security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-icons	AI (dependencies): First-party @fluentui sibling package from Microsoft's monorepo; no security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-theme	AI (dependencies): First-party @fluentui sibling package from Microsoft's monorepo; no security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-button	AI (dependencies): First-party @fluentui sibling package from Microsoft's monorepo; no security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-tabster	AI (dependencies): First-party @fluentui sibling package from Microsoft's monorepo; no security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-utilities	AI (dependencies): First-party @fluentui sibling package from Microsoft's monorepo; no security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-jsx-runtime	AI (dependencies): First-party @fluentui sibling package from Microsoft's monorepo; no security concern.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-shared-contexts	AI (dependencies): First-party @fluentui sibling package from Microsoft's monorepo; no security concern.	ai	2026/04/25
phantom-deps	phantom-dep:@fluentui/react-aria	AI (phantom-deps): Same-org sibling package; phantom dep pattern is common in monorepo component libraries with re-exports.	ai	2026/04/25
phantom-deps	phantom-dep:@fluentui/react-link	AI (phantom-deps): Same-org sibling package; phantom dep pattern is common in monorepo component libraries with re-exports.	ai	2026/04/25

Versions (showing 32 of 32)

Version	Deps	Published
9.4.2	11 / 0	2026-05-26
9.4.1	11 / 0	2026-04-23
9.4.0	11 / 0	2026-03-26
9.3.17	11 / 0	2026-02-25
9.3.16	11 / 0	2026-02-12
9.3.15	11 / 0	2026-01-22
9.3.14	11 / 8	2025-12-17
9.3.13	11 / 8	2025-12-05
9.3.12	11 / 8	2025-11-11
9.3.11	11 / 8	2025-11-06
9.3.10	11 / 8	2025-10-31
9.3.9	11 / 8	2025-10-21
9.3.8	11 / 8	2025-10-08
9.3.7	11 / 8	2025-10-02
9.3.6	11 / 8	2025-09-08
9.3.5	11 / 8	2025-08-21
9.3.4	11 / 8	2025-08-07
9.3.3	11 / 8	2025-07-30
9.3.2	11 / 8	2025-07-30
9.3.1	11 / 8	2025-07-28
9.3.0	11 / 8	2025-07-17
9.2.7	11 / 8	2025-07-11
9.2.6	11 / 8	2025-07-04
9.2.5	11 / 8	2025-06-27
9.2.4	11 / 8	2025-06-26
9.2.3	11 / 8	2025-06-23
9.2.2	11 / 8	2025-06-18
9.2.1	11 / 8	2025-06-13
9.2.0	11 / 8	2025-06-12
9.1.9	11 / 8	2025-06-11
9.1.8	11 / 8	2025-06-06
9.1.7	11 / 8	2025-05-14

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.4.0

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.3.17

1 finding

LOW No provenance attestation provenance

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

v9.3.16

1 finding

LOW No provenance attestation provenance

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

v9.3.15

1 finding

LOW No provenance attestation provenance

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

v9.3.14

1 finding

LOW No provenance attestation provenance

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

v9.3.13

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.3.12

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.3.11

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.3.10

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.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. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.6

1 finding

LOW No provenance attestation provenance

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

v9.3.5

1 finding

LOW No provenance attestation provenance

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

v9.3.4

1 finding

LOW No provenance attestation provenance

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

v9.3.3

1 finding

LOW No provenance attestation provenance

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

v9.3.2

1 finding

LOW No provenance attestation provenance

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

v9.3.1

1 finding

LOW No provenance attestation provenance

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

v9.3.0

1 finding

LOW No provenance attestation provenance

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

v9.2.7

1 finding

LOW No provenance attestation provenance

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

v9.2.6

1 finding

LOW No provenance attestation provenance

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

v9.2.5

1 finding

LOW No provenance attestation provenance

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

v9.2.4

1 finding

LOW No provenance attestation provenance

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

v9.2.3

1 finding

LOW No provenance attestation provenance

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

v9.2.2

1 finding

LOW No provenance attestation provenance

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

v9.2.1

1 finding

LOW No provenance attestation provenance

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

v9.2.0

1 finding

LOW No provenance attestation provenance

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

v9.1.9

1 finding

LOW No provenance attestation provenance

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

v9.1.8

1 finding

LOW No provenance attestation provenance

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

v9.1.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.