@central-icons-react/round-outlined-radius-3-stroke-1
A collection of round outlined React icons with 3px 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:IconSettingsGear4/index.js | AI (source-diff): Minified React SVG icon component; long lines are SVG path data, not obfuscation. Consistent with all other icons in this library. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.mjs | AI (source-diff): ESM variant of the same minified SVG icon; same pattern as all other icons in this library. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): tsup-bundled React icon component; minified single-line output is normal for this icon library. | ai | |
| source-diff | obfuscated-file:IconJson/index.js | AI (source-diff): tsup-bundled React icon component; minified single-line output is normal for this icon library. | ai | |
| source-diff | obfuscated-file:IconRust/index.js | AI (source-diff): tsup-bundled React icon component; minified single-line output is normal for this icon library. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): tsup-bundled React icon component; minified single-line output is normal for this icon library. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): tsup/esbuild minified React SVG icon component; pattern is consistent across all icons in this library. | ai | |
| provenance | no-provenance | AI (provenance): Established icon library with long publish history; lack of provenance is a stable characteristic, not a risk indicator. | 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 | |
| install-scripts | install-script:preinstall | AI (install-scripts): License check script is a documented pattern for this commercial icon library; stable across versions. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.1.246 | 0 / 5 | |
| 1.1.245 | 0 / 5 | |
| 1.1.243 | 0 / 5 | |
| 1.1.237 | 0 / 5 | |
| 1.1.234 | 0 / 5 | |
| 1.1.231 | 0 / 5 | |
| 1.1.227 | 0 / 5 | |
| 1.1.226 | 0 / 5 | |
| 1.1.224 | 0 / 5 | |
| 1.1.222 | 0 / 5 | |
| 1.1.219 | 0 / 5 | |
| 1.1.217 | 0 / 5 | |
| 1.1.216 | 0 / 5 | |
| 1.1.198 | 0 / 5 | |
| 1.1.191 | 0 / 5 | |
| 1.1.185 | 0 / 5 | |
| 1.1.184 | 0 / 5 | |
| 1.1.180 | 0 / 5 | |
| 1.1.176 | 0 / 5 |
v1.1.246
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.245
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.237
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.231
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.227
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.226
1 finding[Accepted risk] Package 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.222
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.219
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.217
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.198
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
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.184
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.