@central-icons-react/round-outlined-radius-0-stroke-1.5
A collection of round outlined 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:IconReact/index.js | AI (source-diff): Same pattern: minified icon component, no suspicious code. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): Same pattern: minified icon component, no suspicious code. | ai | |
| source-diff | obfuscated-file:IconRust/index.js | AI (source-diff): Same pattern: minified icon component, no suspicious code. | ai | |
| source-diff | obfuscated-file:IconJson/index.js | AI (source-diff): Minified React icon component produced by tsup/esbuild; contains only SVG path data and React.createElement, no malicious logic. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): tsup/esbuild minified React SVG icon bundle; pattern is consistent across all versions of this icon library. | ai | |
| provenance | no-provenance | AI (provenance): Established icon library package with trusted publisher; lack of Sigstore attestation is not a security risk here. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon source files across versions; pattern is stable and expected for this package. | 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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 0 / 5 | |
| 1.1.228 | 0 / 5 | |
| 1.1.226 | 0 / 5 | |
| 1.1.223 | 0 / 5 | |
| 1.1.220 | 0 / 5 | |
| 1.1.216 | 0 / 5 | |
| 1.1.199 | 0 / 5 | |
| 1.1.191 | 0 / 5 | |
| 1.1.189 | 0 / 5 | |
| 1.1.187 | 0 / 5 | |
| 1.1.178 | 0 / 5 | |
| 1.1.177 | 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.228
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.223
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.220
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.199
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.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.