← Home

@fluentui/react-drawer

npm Repository Homepage

Drawer components for Fluent UI React

36
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
provenance no-provenance AI (provenance): Established Microsoft Fluent UI package; lack of Sigstore provenance is consistent across the entire @fluentui/* ecosystem and is not a meaningful risk signal here. ai
dependencies unvetted-dep:@griffel/react AI (dependencies): @griffel/react is Microsoft's official CSS-in-JS engine for Fluent UI; a stable, expected dependency for this package. ai
dependencies unvetted-dep:@fluentui/react-theme AI (dependencies): First-party @fluentui/* dependency from the same Microsoft monorepo; expected and legitimate. ai
dependencies unvetted-dep:@fluentui/react-dialog AI (dependencies): First-party @fluentui/* dependency from the same Microsoft monorepo; expected and legitimate. ai
dependencies unvetted-dep:@fluentui/react-motion AI (dependencies): First-party @fluentui/* dependency from the same Microsoft monorepo; expected and legitimate. ai
dependencies unvetted-dep:@fluentui/react-portal AI (dependencies): First-party @fluentui/* dependency from the same Microsoft monorepo; expected and legitimate. ai
dependencies unvetted-dep:@fluentui/react-tabster AI (dependencies): First-party @fluentui/* dependency from the same Microsoft monorepo; expected and legitimate. ai
dependencies unvetted-dep:@fluentui/react-utilities AI (dependencies): First-party @fluentui/* dependency from the same Microsoft monorepo; expected and legitimate. ai
dependencies unvetted-dep:@fluentui/react-jsx-runtime AI (dependencies): First-party @fluentui/* dependency from the same Microsoft monorepo; expected and legitimate. ai
dependencies unvetted-dep:@fluentui/react-shared-contexts AI (dependencies): First-party @fluentui/* dependency from the same Microsoft monorepo; expected and legitimate. ai
dependencies unvetted-dep:@fluentui/react-motion-components-preview AI (dependencies): First-party @fluentui/* dependency from the same Microsoft monorepo; expected and legitimate. ai

Versions (showing 36 of 36)

Version Deps Published
9.13.0 11 / 0
9.12.0 11 / 0
9.11.6 11 / 0
9.11.5 11 / 0
9.11.4 11 / 0
9.11.3 11 / 0
9.11.2 11 / 0
9.11.1 11 / 6
9.11.0 11 / 6
9.10.9 11 / 6
9.10.8 11 / 6
9.10.7 11 / 6
9.10.6 10 / 6
9.10.5 10 / 6
9.10.4 10 / 6
9.10.3 10 / 6
9.10.2 10 / 6
9.10.1 10 / 6
9.10.0 10 / 6
9.9.4 10 / 6
9.9.3 10 / 6
9.9.2 10 / 6
9.9.1 10 / 6
9.9.0 10 / 6
9.8.8 10 / 6
9.8.7 10 / 6
9.8.6 10 / 6
9.8.5 10 / 6
9.8.4 10 / 6
9.8.3 10 / 6
9.8.2 10 / 6
9.8.1 10 / 6
9.8.0 10 / 6
9.7.11 10 / 6
9.7.10 10 / 6
9.7.9 10 / 6

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

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.11.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.11.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.11.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.11.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.11.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.11.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.10.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.10.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.10.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.10.6

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.10.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.10.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.10.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.10.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.10.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.10.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.9.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.9.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.9.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.9.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.9.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.7.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.7.10

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