@central-icons-react-native/round-outlined-radius-0-stroke-1
A collection of round outlined React icons with 0px radius and 1px stroke width, designed for use in React Native / Expo 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:IconJson/index.mjs | AI (source-diff): tsup/esbuild minified ESM icon component; SVG path data on long lines, no malicious code. | ai | |
| source-diff | obfuscated-file:IconReact/index.mjs | AI (source-diff): tsup/esbuild minified ESM icon component; SVG path data on long lines, no malicious code. | ai | |
| source-diff | obfuscated-file:IconJson/index.js | AI (source-diff): tsup/esbuild minified icon component; SVG path data on long lines, no malicious code. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): tsup/esbuild minified icon component; SVG path data on long lines, no malicious code. | ai | |
| source-diff | obfuscated-file:IconRust/index.js | AI (source-diff): tsup/esbuild minified icon component; SVG path data on long lines, no malicious code. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): tsup/esbuild minified icon component; SVG path data on long lines, no malicious code. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 244 versions; not a per-version risk signal for this package. | 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. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License enforcement script (license-check.js) is standard for commercial icon libraries; stable pattern across this package family. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 1 / 5 | |
| 1.1.226 | 1 / 5 | |
| 1.1.224 | 1 / 5 | |
| 1.1.198 | 1 / 5 | |
| 1.1.191 | 1 / 5 | |
| 1.1.190 | 1 / 5 | |
| 1.1.178 | 1 / 5 |
v1.1.234
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.198
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.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.190
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. Only ~12% of npm packages have provenance, so this is common but not ideal.