@central-icons-react/round-filled-radius-2-stroke-2
A collection of round filled React icons with 2px radius and 2px stroke width, designed for use in React applications.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:IconFullMoon/index.mjs | AI (source-diff): Bundled tsup ESM output for React icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): tsup-bundled CJS output for SVG icon component; minified single-line format is expected for this icon library. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.js | AI (source-diff): tsup-bundled CJS output for SVG icon component; minified single-line format is expected for this icon library. | ai | |
| source-diff | obfuscated-file:IconGraduateCap2/index.js | AI (source-diff): Minified output from tsup build tool; code samples show legitimate React SVG icon components. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.js | AI (source-diff): Minified output from tsup build tool; code samples show legitimate React SVG icon components. | ai | |
| source-diff | obfuscated-file:IconJson/index.js | AI (source-diff): Minified output from tsup build tool; code samples show legitimate React SVG icon components. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): Minified output from tsup build tool; code samples show legitimate React SVG icon components. | ai | |
| source-diff | obfuscated-file:IconRust/index.js | AI (source-diff): Minified output from tsup build tool; code samples show legitimate React SVG icon components. | ai | |
| source-diff | obfuscated-file:IconSendLater/index.js | AI (source-diff): Minified output from tsup build tool; code samples show legitimate React SVG icon components. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): Minified output from tsup build tool; code samples show legitimate React SVG icon components. | ai | |
| source-diff | obfuscated-file:IconAnimatePath/index.mjs | AI (source-diff): Minified output from tsup build tool; consistent with other icon component files. | ai | |
| source-diff | obfuscated-file:IconAnimatePath/index.js | AI (source-diff): Minified output from tsup build tool; code samples show legitimate React SVG icon components, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Minified tsup/esbuild output containing only SVG React components; no malicious code patterns. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): Minified tsup/esbuild output containing only SVG React components; no malicious code patterns. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library grows by adding new icon components; large file counts are expected for this package type. | ai | |
| source-diff | obfuscated-file:IconSunLow/index.js | AI (source-diff): Minified tsup/esbuild output containing only SVG React components; no malicious code patterns. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.js | AI (source-diff): Minified tsup/esbuild output containing only SVG React components; no malicious code patterns. | ai | |
| source-diff | obfuscated-file:IconSunHigh/index.js | AI (source-diff): Minified tsup/esbuild output containing only SVG React components; no malicious code patterns. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License enforcement script (license-check.js) is a stable, benign pattern for this commercial icon library across all versions. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 0 / 5 | |
| 1.1.230 | 0 / 5 | |
| 1.1.222 | 0 / 5 | |
| 1.1.221 | 0 / 5 | |
| 1.1.220 | 0 / 5 | |
| 1.1.219 | 0 / 5 | |
| 1.1.218 | 0 / 5 | |
| 1.1.217 | 0 / 5 | |
| 1.1.216 | 0 / 5 | |
| 1.1.199 | 0 / 5 | |
| 1.1.192 | 0 / 5 | |
| 1.1.190 | 0 / 5 | |
| 1.1.184 | 0 / 5 | |
| 1.1.179 | 0 / 5 |
v1.1.234
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.230
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.222
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.221
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.219
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.199
12 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.192
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.190
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.184
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.