@central-icons-react/round-filled-radius-0-stroke-1.5
A collection of round filled React icons with 0px 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:IconReduceMotion/index.js | AI (source-diff): Same minified icon component pattern; not obfuscation. | ai | |
| source-diff | obfuscated-file:IconVoiceover2/index.js | AI (source-diff): Same minified icon component pattern; not obfuscation. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; consistent with this icon library's build output pattern. | ai | |
| source-diff | obfuscated-file:IconGraduateCap2/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; consistent with this icon library's build output pattern. | ai | |
| source-diff | obfuscated-file:IconSendLater/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; consistent with this icon library's build output pattern. | ai | |
| source-diff | obfuscated-file:IconSunHigh/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; consistent with this icon library's build output pattern. | ai | |
| source-diff | obfuscated-file:IconSunLow/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; consistent with this icon library's build output pattern. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; consistent with this icon library's build output pattern. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.mjs | AI (source-diff): tsup/esbuild minified React SVG icon component ESM variant; consistent with this icon library's build output pattern. | ai | |
| source-diff | obfuscated-file:IconReact/index.mjs | AI (source-diff): tsup/esbuild minified React SVG icon component ESM variant; consistent with this icon library's build output pattern. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; consistent with this icon library's build output pattern. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files across versions; large file additions are expected for this package. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): Minified CJS bundle output from tsup/esbuild; contains only React SVG icon components, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.mjs | AI (source-diff): Minified tsup/esbuild output for SVG icon component; no malicious patterns, consistent with this icon library's build process. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Minified tsup/esbuild output for SVG icon component; no malicious patterns, consistent with this icon library's build process. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.js | AI (source-diff): Minified tsup/esbuild output for SVG icon component; no malicious patterns, consistent with this icon library's build process. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): Minified tsup/esbuild output for SVG icon component; no malicious patterns, consistent with this icon library's build process. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Runs local license-check.js only; consistent commercial license enforcement pattern across all versions of this icon library. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.1.247 | 0 / 5 | |
| 1.1.237 | 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.221 | 0 / 5 | |
| 1.1.216 | 0 / 5 | |
| 1.1.196 | 0 / 5 | |
| 1.1.189 | 0 / 5 | |
| 1.1.185 | 0 / 5 | |
| 1.1.182 | 0 / 5 | |
| 1.1.181 | 0 / 5 | |
| 1.1.180 | 0 / 5 | |
| 1.1.179 | 0 / 5 | |
| 1.1.178 | 0 / 5 | |
| 1.1.177 | 0 / 5 | |
| 1.1.175 | 0 / 5 |
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.237
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.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.221
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.196
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.189
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
7 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.
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.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.