@central-icons-react/round-filled-radius-2-stroke-1.5
A collection of round filled React icons with 2px radius and 1.5px 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): Standard tsup/esbuild minified React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconGraduateCap2/index.js | AI (source-diff): Standard tsup/esbuild minified React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.js | AI (source-diff): Standard tsup/esbuild minified React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconReact/index.mjs | AI (source-diff): Standard tsup/esbuild minified React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): Standard tsup/esbuild minified React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconSendLater/index.js | AI (source-diff): Standard tsup/esbuild minified React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): Standard tsup/esbuild minified React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconVoiceover2/index.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:IconReduceMotion/index.js | AI (source-diff): Minified React icon component; tsup build output, no malicious patterns. | ai | |
| source-diff | obfuscated-file:IconReduceMotion/index.mjs | AI (source-diff): Minified ESM React icon component; tsup build output, no malicious patterns. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.mjs | AI (source-diff): ESM variant of same tsup bundle; no malicious content. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): tsup-bundled React icon component; long lines are minified SVG+React output, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.js | AI (source-diff): Same tsup bundle pattern; SVG path data and React.createElement only. | ai | |
| source-diff | obfuscated-file:IconSunHigh/index.js | AI (source-diff): Minified tsup/esbuild output of React SVG icon components; standard build artifact for this icon library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files across versions; large file counts are expected growth. | ai | |
| source-diff | obfuscated-file:IconSunLow/index.js | AI (source-diff): Minified tsup/esbuild output of React SVG icon components; standard build artifact for this icon library. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): tsup-bundled React icon component; long lines are minified SVG paths, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.js | AI (source-diff): tsup-bundled React icon component; long lines are minified SVG paths, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): tsup-bundled ESM React icon component; same pattern as CJS counterpart. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.mjs | AI (source-diff): tsup-bundled ESM React icon component; same pattern as CJS counterpart. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License check script only; stable pattern across all versions of this commercial icon package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.1.249 | 0 / 5 | |
| 1.1.248 | 0 / 5 | |
| 1.1.247 | 0 / 5 | |
| 1.1.241 | 0 / 5 | |
| 1.1.240 | 0 / 5 | |
| 1.1.239 | 0 / 5 | |
| 1.1.238 | 0 / 5 | |
| 1.1.237 | 0 / 5 | |
| 1.1.236 | 0 / 5 | |
| 1.1.234 | 0 / 5 | |
| 1.1.225 | 0 / 5 | |
| 1.1.224 | 0 / 5 | |
| 1.1.223 | 0 / 5 | |
| 1.1.216 | 0 / 5 | |
| 1.1.195 | 0 / 5 | |
| 1.1.187 | 0 / 5 | |
| 1.1.186 | 0 / 5 | |
| 1.1.185 | 0 / 5 | |
| 1.1.182 | 0 / 5 | |
| 1.1.179 | 0 / 5 | |
| 1.1.178 | 0 / 5 | |
| 1.1.177 | 0 / 5 | |
| 1.1.176 | 0 / 5 | |
| 1.1.175 | 0 / 5 |
v1.1.249
2 findingsNewly 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.248
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.247
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.241
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.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.236
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.234
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.225
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.224
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.223
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.195
10 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.187
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.186
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.185
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.182
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.
v1.1.178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.