@central-icons-react-native/round-filled-radius-2-stroke-2
A collection of round filled React icons with 2px 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): Bundled tsup/esbuild output for SVG icon components; long lines are standard for this icon library's build output. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Standard tsup/esbuild bundle output for SVG icon components; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:IconSunHigh/index.js | AI (source-diff): Standard tsup/esbuild bundle output for SVG icon components; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:IconSunLow/index.js | AI (source-diff): Standard tsup/esbuild bundle output for SVG icon components; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): Standard tsup/esbuild bundle output for SVG icon components; not malicious obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files; large file counts are expected for this package. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.js | AI (source-diff): Bundled tsup/esbuild output for SVG icon components; long lines are standard for this icon library package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Runs license-check.js only; consistent commercial license enforcement pattern across all versions of this icon library. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 1 / 5 | |
| 1.1.228 | 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.191 | 1 / 5 | |
| 1.1.190 | 1 / 5 | |
| 1.1.189 | 1 / 5 | |
| 1.1.177 | 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.228
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.191
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.190
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.189
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.177
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.