← Home

@fluentui/react-switch

npm Repository Homepage

Fluent UI React Switch component.

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

chrisdholtmiroslavstastnylevithomasonuifabricteamuifrnbotlayershifterjustslonemicrosoft1essopranopillow

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@griffel/react AI (dependencies): @griffel/react is Microsoft's official CSS-in-JS library for Fluent UI v9; a legitimate first-party dependency for all @fluentui/* packages. ai
dependencies unvetted-dep:@fluentui/react-field AI (dependencies): First-party @fluentui/* dependency from the same microsoft/fluentui monorepo; not a third-party risk. ai
dependencies unvetted-dep:@fluentui/react-icons AI (dependencies): First-party @fluentui/* dependency from the same microsoft/fluentui monorepo; not a third-party risk. ai
dependencies unvetted-dep:@fluentui/react-label AI (dependencies): First-party @fluentui/* dependency from the same microsoft/fluentui monorepo; not a third-party risk. ai
dependencies unvetted-dep:@fluentui/react-theme AI (dependencies): First-party @fluentui/* dependency from the same microsoft/fluentui monorepo; not a third-party risk. ai
dependencies unvetted-dep:@fluentui/react-tabster AI (dependencies): First-party @fluentui/* dependency from the same microsoft/fluentui monorepo; not a third-party risk. ai
dependencies unvetted-dep:@fluentui/react-utilities AI (dependencies): First-party @fluentui/* dependency from the same microsoft/fluentui monorepo; not a third-party risk. ai
dependencies unvetted-dep:@fluentui/react-jsx-runtime AI (dependencies): First-party @fluentui/* dependency from the same microsoft/fluentui monorepo; not a third-party risk. ai
dependencies unvetted-dep:@fluentui/react-shared-contexts AI (dependencies): First-party @fluentui/* dependency from the same microsoft/fluentui monorepo; not a third-party risk. ai
provenance no-provenance AI (provenance): Established Microsoft Fluent UI package published from a known team account; lack of Sigstore provenance is not a meaningful risk signal here. ai

Versions (showing 34 of 34)

Version Deps Published
9.7.3 10 / 0
9.7.2 10 / 0
9.7.1 10 / 0
9.7.0 10 / 0
9.6.1 10 / 0
9.6.0 10 / 0
9.5.4 10 / 0
9.5.3 10 / 0
9.5.2 10 / 0
9.5.1 10 / 4
9.5.0 10 / 4
9.4.11 10 / 4
9.4.10 10 / 4
9.4.9 10 / 4
9.4.8 10 / 4
9.4.7 10 / 4
9.4.6 10 / 4
9.4.5 10 / 4
9.4.4 10 / 4
9.4.3 10 / 4
9.4.2 10 / 4
9.4.1 10 / 4
9.4.0 10 / 4
9.3.7 10 / 4
9.3.6 10 / 4
9.3.5 10 / 4
9.3.4 10 / 4
9.3.3 10 / 4
9.3.2 10 / 4
9.3.1 10 / 4
9.3.0 10 / 4
9.2.9 10 / 4
9.2.8 10 / 4
9.2.7 10 / 4

v9.7.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.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
INFO No provenance attestation provenance

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

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

v9.6.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.6.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.5.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.5.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.5.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.5.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.5.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.4.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.4.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.4.9

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

v9.2.7

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.