@central-icons-react/round-outlined-radius-1-stroke-2
A collection of round outlined React icons with 1px 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:IconReact/index.mjs | AI (source-diff): tsup/esbuild minified output for SVG icon components; stable pattern for this icon library package. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): tsup/esbuild minified output for SVG icon components; stable pattern for this icon library package. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): tsup/esbuild minified output for SVG icon components; stable pattern for this icon library package. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.mjs | AI (source-diff): Minified React icon component ESM bundle; SVG path data visible in sample, no malicious patterns. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): Minified React icon component bundle; SVG path data visible in sample, no malicious patterns. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.js | AI (source-diff): Minified React icon component bundle; SVG path data visible in sample, no malicious patterns. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files per version; large file additions are expected and not suspicious. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License-check script is a documented commercial enforcement pattern for this icon library; stable across versions. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 0 / 5 | |
| 1.1.232 | 0 / 5 | |
| 1.1.226 | 0 / 5 | |
| 1.1.225 | 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.196 | 0 / 5 | |
| 1.1.189 | 0 / 5 | |
| 1.1.188 | 0 / 5 | |
| 1.1.186 | 0 / 5 | |
| 1.1.185 | 0 / 5 | |
| 1.1.180 | 0 / 5 | |
| 1.1.177 | 0 / 5 | |
| 1.1.176 | 0 / 5 | |
| 1.1.175 | 0 / 5 |
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.232
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.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.196
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.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.185
1 findingPackage 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.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.