@central-icons-react/round-filled-radius-2-stroke-1
A collection of round filled React icons with 2px radius and 1px 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.mjs | AI (source-diff): Same pattern as .js counterpart; standard bundled ESM icon component. | ai | |
| source-diff | obfuscated-file:IconReduceMotion/index.js | AI (source-diff): Minified React icon component with SVG path data; long lines are from coordinate strings, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; long lines are build artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.mjs | AI (source-diff): tsup/esbuild minified React SVG icon component; long lines are build artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; long lines are build artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.mjs | AI (source-diff): Minified tsup/esbuild ESM output of a React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.js | AI (source-diff): Minified tsup/esbuild output of a React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconSunHigh/index.js | AI (source-diff): Minified tsup/esbuild output of a React SVG icon component; no malicious code. | ai | |
| source-diff | obfuscated-file:IconSunLow/index.js | AI (source-diff): Minified tsup/esbuild output of a React SVG icon component; no malicious code. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library adds new icon files per release; large file counts are expected and benign. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): ESM variant of same tsup bundle; SVG path coordinates cause long lines. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Same tsup bundle pattern with SVG path data; not obfuscation. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.js | AI (source-diff): Long lines are SVG path coordinate data in tsup-bundled output, not obfuscation. Stable pattern for this icon library. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Runs local license-check.js only; stable commercial icon library pattern across all versions. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 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.192 | 0 / 5 | |
| 1.1.189 | 0 / 5 | |
| 1.1.188 | 0 / 5 | |
| 1.1.181 | 0 / 5 | |
| 1.1.178 | 0 / 5 | |
| 1.1.177 | 0 / 5 | |
| 1.1.176 | 0 / 5 | |
| 1.1.175 | 0 / 5 |
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.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.189
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.188
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.181
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.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.