@central-icons-react-native/round-filled-radius-2-stroke-1
A collection of round filled React icons with 2px 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:IconSettingsGear4/index.js | AI (source-diff): Minified tsup/esbuild bundle output for SVG icon components; consistent pattern across all versions of this icon library. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.js | AI (source-diff): tsup-bundled SVG icon component; minified but contains only SVG path data and React.createElement calls. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.mjs | AI (source-diff): ESM variant of same tsup bundle; SVG icon component only. | ai | |
| source-diff | obfuscated-file:IconSunLow/index.js | AI (source-diff): Minified tsup bundle of SVG icon component; no malicious code, consistent with package purpose. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library adds new icons per release; 54 new files is expected growth pattern for this package. | ai | |
| source-diff | obfuscated-file:IconSunHigh/index.js | AI (source-diff): Minified tsup bundle of SVG icon component; no malicious code, consistent with package purpose. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Same tsup bundle pattern; SVG path data in minified React createElement calls. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.js | AI (source-diff): tsup-bundled SVG icon component; long lines are SVG path data in minified React createElement calls. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): ESM variant of same tsup-bundled SVG icon; not obfuscated. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Runs local license-check.js only; consistent with commercial icon library license enforcement across all versions. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 1 / 5 | |
| 1.1.232 | 1 / 5 | |
| 1.1.226 | 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.220 | 1 / 5 | |
| 1.1.219 | 1 / 5 | |
| 1.1.217 | 1 / 5 | |
| 1.1.216 | 1 / 5 | |
| 1.1.193 | 1 / 5 | |
| 1.1.188 | 1 / 5 | |
| 1.1.183 | 1 / 5 | |
| 1.1.181 | 1 / 5 | |
| 1.1.179 | 1 / 5 | |
| 1.1.177 | 1 / 5 | |
| 1.1.176 | 1 / 5 | |
| 1.1.175 | 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.232
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.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.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.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.193
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.188
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.183
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.181
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.179
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.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.176
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.