@central-icons-react-native/round-outlined-radius-1-stroke-1.5
A collection of round outlined React icons with 1px radius and 1.5px 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:IconRust/index.js | AI (source-diff): tsup/esbuild minified icon component output; legitimate React Native SVG icon code. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): tsup/esbuild minified icon component output; legitimate React Native SVG icon code. | ai | |
| source-diff | obfuscated-file:IconJson/index.js | AI (source-diff): tsup/esbuild minified icon component output; SVG path data and React createElement calls visible in sample. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): tsup/esbuild minified icon component output; legitimate React Native SVG icon code. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.mjs | AI (source-diff): Minified ESM icon component bundle; same pattern as CJS counterpart, readable SVG/React code. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.js | AI (source-diff): Minified icon component bundle; content is readable SVG/React code, not obfuscation. Stable pattern for this icon library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon source files per version; pattern is stable and expected. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License enforcement script (node ./license-check.js) is consistent with commercial icon library pattern; stable across versions. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 1 / 5 | |
| 1.1.230 | 1 / 5 | |
| 1.1.228 | 1 / 5 | |
| 1.1.227 | 1 / 5 | |
| 1.1.225 | 1 / 5 | |
| 1.1.224 | 1 / 5 | |
| 1.1.223 | 1 / 5 | |
| 1.1.222 | 1 / 5 | |
| 1.1.221 | 1 / 5 | |
| 1.1.219 | 1 / 5 | |
| 1.1.218 | 1 / 5 | |
| 1.1.217 | 1 / 5 | |
| 1.1.216 | 1 / 5 | |
| 1.1.198 | 1 / 5 | |
| 1.1.187 | 1 / 5 | |
| 1.1.182 | 1 / 5 | |
| 1.1.181 | 1 / 5 | |
| 1.1.180 | 1 / 5 | |
| 1.1.179 | 1 / 5 | |
| 1.1.175 | 1 / 5 |
v1.1.234
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.230
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.228
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.227
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.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.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.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.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.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.179
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.