@fluentui/react-icons-compat MIT 22 versions

@fluentui/react-icons-compat

npm Repository Homepage

Package for icon utility methods used by font and svg icons.

22

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
phantom-deps	phantom-dep:@swc/helpers	AI (phantom-deps): SWC runtime helper; implicit dependency from transpilation.	ai	2026/04/29
phantom-deps	phantom-dep:@griffel/react	AI (phantom-deps): Config-referenced styling dependency; stable for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@fluentui/react-theme	AI (phantom-deps): Same-org peer utility; stable monorepo pattern.	ai	2026/04/29
phantom-deps	phantom-dep:@fluentui/react-jsx-runtime	AI (phantom-deps): Same-org peer utility; stable monorepo pattern.	ai	2026/04/29
phantom-deps	phantom-dep:@fluentui/react-shared-contexts	AI (phantom-deps): Same-org peer utility; stable monorepo pattern.	ai	2026/04/29

Versions (showing 22 of 22)

Version	Deps	Published
0.2.20	6 / 0	2026-05-26
0.2.19	6 / 0	2026-04-23
0.2.18	6 / 0	2026-02-25
0.2.17	6 / 0	2026-02-12
0.2.16	6 / 0	2026-01-22
0.2.15	6 / 4	2025-12-17
0.2.14	6 / 4	2025-11-11
0.2.13	6 / 4	2025-11-06
0.2.12	6 / 4	2025-10-31
0.2.11	6 / 4	2025-10-21
0.2.10	6 / 4	2025-10-08
0.2.9	6 / 4	2025-10-02
0.2.8	6 / 4	2025-09-08
0.2.7	6 / 4	2025-08-21
0.2.6	6 / 4	2025-08-07
0.2.5	6 / 4	2025-07-30
0.2.4	6 / 4	2025-07-28
0.2.3	6 / 4	2025-07-17
0.2.2	6 / 4	2025-06-26
0.2.1	6 / 4	2025-06-18
0.2.0	6 / 4	2025-06-12
0.1.13	6 / 4	2025-06-06

v0.2.20

1 finding

LOW No provenance attestation provenance

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

v0.2.18

1 finding

LOW No provenance attestation provenance

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

v0.2.17

1 finding

LOW No provenance attestation provenance

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

v0.2.16

1 finding

LOW No provenance attestation provenance

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

v0.2.15

1 finding

LOW No provenance attestation provenance

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

v0.2.14

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.

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

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

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

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

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