@firesoon/icons-react — Greenflagged

火树图标库

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

firesoon-uedmaoliziink0101tangshuoanglaychenweimingwxshycatlinweili1201npm_fwjzhouyx

Keywords

svgjavascripttypescriptreact

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:es/icons/fs/business-menu/fs-expert.js	AI (source-diff): Long lines are SVG path data in an icon library; not obfuscated executable code.	ai	2026/05/10
source-diff	obfuscated-file:lib/icons/fs/business-menu/fs-expert.js	AI (source-diff): Long lines are SVG path data in an icon library; not obfuscated executable code.	ai	2026/05/10

Versions (showing 23 of 23)

Version	Deps	Published
3.1.10	0 / 42	2026-06-05
3.1.9	0 / 42	2026-05-19
3.1.8	0 / 42	2026-04-28
3.1.7	0 / 42	2026-04-27
3.1.6	0 / 42	2026-04-27
3.1.3	0 / 42	2025-12-09
3.1.2	0 / 42	2025-11-24
3.1.1	0 / 42	2025-11-20
3.1.0	0 / 42	2025-11-20
3.0.40	0 / 42	2025-11-04
3.0.39	0 / 42	2025-10-20
3.0.38	0 / 42	2025-10-14
3.0.37	0 / 42	2025-10-13
3.0.36	0 / 42	2025-09-10
3.0.35	0 / 42	2025-08-12
3.0.34	0 / 23	2025-07-15
3.0.33	0 / 23	2025-07-09
3.0.32	0 / 23	2025-07-07
3.0.31	0 / 23	2025-07-01
3.0.30	0 / 23	2025-06-19
3.0.29	0 / 23	2025-06-19
3.0.28	0 / 23	2025-05-27
3.0.27	0 / 23	2025-05-26

v3.1.10

1 finding

LOW No provenance attestation provenance

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

v3.1.9

1 finding

LOW No provenance attestation provenance

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

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

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

v3.1.3

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

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

v3.0.40

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.

v3.0.39

1 finding

LOW No provenance attestation provenance

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

v3.0.38

1 finding

LOW No provenance attestation provenance

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

v3.0.37

1 finding

LOW No provenance attestation provenance

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

v3.0.36

1 finding

LOW No provenance attestation provenance

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

v3.0.35

1 finding

LOW No provenance attestation provenance

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

v3.0.34

3 findings

HIGH New obfuscated file: es/icons/fs/business-menu/fs-expert.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: lib/icons/fs/business-menu/fs-expert.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v3.0.33

1 finding

LOW No provenance attestation provenance

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

v3.0.32

1 finding

LOW No provenance attestation provenance

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

v3.0.31

1 finding

LOW No provenance attestation provenance

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

v3.0.30

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.

v3.0.29

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.

v3.0.28

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.

v3.0.27

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.