@central-icons-react/round-filled-radius-0-stroke-2
A collection of round filled React icons with 0px 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.js | AI (source-diff): tsup/esbuild minified React icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.mjs | AI (source-diff): tsup/esbuild minified React icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSunLow/index.js | AI (source-diff): tsup/esbuild minified React icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSunHigh/index.js | AI (source-diff): tsup/esbuild minified React icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): Minified tsup/esbuild bundle output for React SVG icon components; stable pattern for this icon library package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files across versions; large file counts are expected and benign. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.js | AI (source-diff): Minified tsup/esbuild output of SVG icon components; standard build artifact for this icon library. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): Minified tsup/esbuild output of SVG icon components; standard build artifact for this icon library. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.mjs | AI (source-diff): Minified tsup/esbuild output of SVG icon components; standard build artifact for this icon library. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Minified tsup/esbuild output of SVG icon components; standard build artifact for this icon library. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Runs license-check.js only; consistent commercial license enforcement pattern across all 275 versions of this icon library. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 0 / 5 | |
| 1.1.233 | 0 / 5 | |
| 1.1.232 | 0 / 5 | |
| 1.1.230 | 0 / 5 | |
| 1.1.228 | 0 / 5 | |
| 1.1.226 | 0 / 5 | |
| 1.1.225 | 0 / 5 | |
| 1.1.224 | 0 / 5 | |
| 1.1.223 | 0 / 5 | |
| 1.1.222 | 0 / 5 | |
| 1.1.221 | 0 / 5 | |
| 1.1.220 | 0 / 5 | |
| 1.1.219 | 0 / 5 | |
| 1.1.217 | 0 / 5 | |
| 1.1.216 | 0 / 5 | |
| 1.1.193 | 0 / 5 | |
| 1.1.192 | 0 / 5 | |
| 1.1.191 | 0 / 5 | |
| 1.1.182 | 0 / 5 | |
| 1.1.180 | 0 / 5 | |
| 1.1.177 | 0 / 5 | |
| 1.1.175 | 0 / 5 |
v1.1.234
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.233
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.232
1 findingPackage 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.228
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.226
1 findingPackage 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.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.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.193
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.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.191
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.180
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.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.