@central-icons-react-native/round-filled-radius-0-stroke-1.5
A collection of round filled React icons with 0px 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:IconReduceMotion/index.mjs | AI (source-diff): ESM bundler output for SVG icon component; same pattern as all other icons in this package. | ai | |
| source-diff | obfuscated-file:IconReduceMotion/index.js | AI (source-diff): Minified bundler output (tsup/esbuild) for SVG icon components; consistent with all other icons in this package. | ai | |
| source-diff | obfuscated-file:IconSunHigh/index.js | AI (source-diff): Minified tsup bundle of SVG icon component; no malicious content, stable pattern for this icon library. | ai | |
| source-diff | obfuscated-file:IconSunLow/index.js | AI (source-diff): Minified tsup bundle of SVG icon component; no malicious content, stable pattern for this icon library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files per version; large file counts are expected and benign. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): Minified tsup ESM bundle of SVG icon component; no malicious content, stable pattern for this icon library. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Minified tsup bundle of SVG icon component; no malicious content, stable pattern for this icon library. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License enforcement script (license-check.js) is expected for this commercial icon library; stable pattern across versions. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.1.241 | 1 / 5 | |
| 1.1.240 | 1 / 5 | |
| 1.1.239 | 1 / 5 | |
| 1.1.238 | 1 / 5 | |
| 1.1.237 | 1 / 5 | |
| 1.1.236 | 1 / 5 | |
| 1.1.235 | 1 / 5 | |
| 1.1.234 | 1 / 5 | |
| 1.1.233 | 1 / 5 | |
| 1.1.230 | 1 / 5 | |
| 1.1.229 | 1 / 5 | |
| 1.1.228 | 1 / 5 | |
| 1.1.227 | 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.218 | 1 / 5 | |
| 1.1.217 | 1 / 5 | |
| 1.1.216 | 1 / 5 | |
| 1.1.190 | 1 / 5 | |
| 1.1.185 | 1 / 5 | |
| 1.1.180 | 1 / 5 | |
| 1.1.179 | 1 / 5 | |
| 1.1.177 | 1 / 5 | |
| 1.1.176 | 1 / 5 |
v1.1.241
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.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.236
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.233
1 findingPackage 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.229
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.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.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.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.185
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.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.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.