@fluentui/react-tabs MIT 25 versions

@fluentui/react-tabs

npm Repository Homepage

Fluent UI React tabs components

25

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 Microsoft's official CSS-in-JS engine for Fluent UI, maintained in the same ecosystem. Stable legitimate dependency for all @fluentui/* packages.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-theme	AI (dependencies): First-party @fluentui/* sibling package from the Microsoft fluentui monorepo. Expected dependency for this component.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-tabster	AI (dependencies): First-party @fluentui/* sibling package from the Microsoft fluentui monorepo. Expected dependency for this component.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-utilities	AI (dependencies): First-party @fluentui/* sibling package from the Microsoft fluentui monorepo. Expected dependency for this component.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-jsx-runtime	AI (dependencies): First-party @fluentui/* sibling package from the Microsoft fluentui monorepo. Expected dependency for this component.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-shared-contexts	AI (dependencies): First-party @fluentui/* sibling package from the Microsoft fluentui monorepo. Expected dependency for this component.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-context-selector	AI (dependencies): First-party @fluentui/* sibling package from the Microsoft fluentui monorepo. Expected dependency for this component.	ai	2026/04/25

Versions (showing 25 of 25)

Version	Deps	Published
9.12.2	8 / 0	2026-05-26
9.12.1	8 / 0	2026-04-23
9.12.0	8 / 0	2026-04-01
9.11.2	8 / 0	2026-02-25
9.11.1	8 / 0	2026-02-12
9.11.0	8 / 0	2026-01-22
9.10.8	8 / 4	2025-12-17
9.10.7	8 / 4	2025-11-11
9.10.6	8 / 4	2025-11-06
9.10.5	8 / 4	2025-10-31
9.10.4	8 / 4	2025-10-21
9.10.3	8 / 4	2025-10-08
9.10.2	8 / 4	2025-10-02
9.10.1	8 / 4	2025-09-08
9.10.0	8 / 4	2025-08-21
9.9.3	8 / 4	2025-08-07
9.9.2	8 / 4	2025-07-30
9.9.1	8 / 4	2025-07-28
9.9.0	8 / 4	2025-07-17
9.8.3	8 / 4	2025-06-27
9.8.2	8 / 4	2025-06-26
9.8.1	8 / 4	2025-06-18
9.8.0	8 / 4	2025-06-12
9.7.8	8 / 4	2025-06-06
9.7.7	8 / 4	2025-05-14

v9.12.2

1 finding

LOW No provenance attestation provenance

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

v9.12.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.12.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.11.2

1 finding

LOW No provenance attestation provenance

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

v9.11.1

1 finding

LOW No provenance attestation provenance

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

v9.11.0

1 finding

LOW No provenance attestation provenance

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

v9.10.8

1 finding

LOW No provenance attestation provenance

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

v9.10.7

1 finding

LOW No provenance attestation provenance

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

v9.10.6

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

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

1 finding

LOW No provenance attestation provenance

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

v9.10.3

1 finding

LOW No provenance attestation provenance

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

v9.10.2

1 finding

LOW No provenance attestation provenance

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

v9.10.1

1 finding

LOW No provenance attestation provenance

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

v9.10.0

1 finding

LOW No provenance attestation provenance

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

v9.9.3

1 finding

LOW No provenance attestation provenance

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

v9.9.2

1 finding

LOW No provenance attestation provenance

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

v9.9.1

1 finding

LOW No provenance attestation provenance

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

v9.9.0

1 finding

LOW No provenance attestation provenance

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

v9.8.3

1 finding

LOW No provenance attestation provenance

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

v9.8.2

1 finding

LOW No provenance attestation provenance

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

v9.8.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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