← Home

@fluentui/react-card

npm Repository Homepage

Card container components for Fluent UI React.

27
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, expected dependency of all @fluentui/react-* components. ai
dependencies unvetted-dep:@fluentui/react-text AI (dependencies): First-party Fluent UI v9 sibling package from the microsoft/fluentui monorepo; expected dependency. ai
dependencies unvetted-dep:@fluentui/react-theme AI (dependencies): First-party Fluent UI v9 sibling package from the microsoft/fluentui monorepo; expected dependency. ai
dependencies unvetted-dep:@fluentui/keyboard-keys AI (dependencies): First-party Fluent UI v9 sibling package from the microsoft/fluentui monorepo; expected dependency. ai
dependencies unvetted-dep:@fluentui/react-tabster AI (dependencies): First-party Fluent UI v9 sibling package from the microsoft/fluentui monorepo; expected dependency. ai
dependencies unvetted-dep:@fluentui/react-utilities AI (dependencies): First-party Fluent UI v9 sibling package from the microsoft/fluentui monorepo; expected dependency. ai
dependencies unvetted-dep:@fluentui/react-jsx-runtime AI (dependencies): First-party Fluent UI v9 sibling package from the microsoft/fluentui monorepo; expected dependency. ai
dependencies unvetted-dep:@fluentui/react-shared-contexts AI (dependencies): First-party Fluent UI v9 sibling package from the microsoft/fluentui monorepo; expected dependency. ai
provenance no-provenance AI (provenance): Established Microsoft Fluent UI package published by uifabricteam; lack of Sigstore provenance is consistent across the entire @fluentui/* ecosystem and not a risk signal here. ai

Versions (showing 27 of 27)

Version Deps Published
9.7.0 9 / 0
9.6.1 9 / 0
9.6.0 9 / 0
9.5.11 9 / 0
9.5.10 9 / 0
9.5.9 9 / 0
9.5.8 9 / 7
9.5.7 9 / 7
9.5.6 9 / 7
9.5.5 9 / 7
9.5.4 9 / 7
9.5.3 9 / 7
9.5.2 9 / 7
9.5.1 9 / 7
9.5.0 9 / 7
9.4.5 9 / 7
9.4.4 9 / 7
9.4.3 9 / 7
9.4.2 9 / 7
9.4.1 9 / 7
9.4.0 9 / 7
9.3.3 9 / 7
9.3.2 9 / 7
9.3.1 9 / 7
9.3.0 9 / 7
9.2.7 9 / 7
9.2.6 9 / 7

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

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

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