@central-icons-react-native/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 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:IconSettingsGear4/index.js | AI (source-diff): Minified tsup/esbuild bundle output for SVG icon components; pattern is stable across all versions of this icon library. | ai | |
| source-diff | obfuscated-file:IconReact/index.mjs | AI (source-diff): Minified tsup/esbuild bundle output for SVG icon components; no malicious patterns. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): Content is esbuild-minified React Native SVG icon component, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:IconRust/index.js | AI (source-diff): Content is esbuild-minified React Native SVG icon component, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): Content is esbuild-minified React Native SVG icon component, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:IconJson/index.js | AI (source-diff): Content is esbuild-minified React Native SVG icon component, not malicious obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon pack regularly adds new icon files across versions; large file additions are expected for this package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Runs license-check.js only; consistent with commercial icon library license enforcement across all versions. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 1 / 5 | |
| 1.1.229 | 1 / 5 | |
| 1.1.226 | 1 / 5 | |
| 1.1.225 | 1 / 5 | |
| 1.1.222 | 1 / 5 | |
| 1.1.221 | 1 / 5 | |
| 1.1.220 | 1 / 5 | |
| 1.1.219 | 1 / 5 | |
| 1.1.218 | 1 / 5 | |
| 1.1.217 | 1 / 5 | |
| 1.1.216 | 1 / 5 | |
| 1.1.199 | 1 / 5 | |
| 1.1.197 | 1 / 5 | |
| 1.1.194 | 1 / 5 | |
| 1.1.187 | 1 / 5 | |
| 1.1.183 | 1 / 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.229
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.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.197
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.194
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.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.