@central-icons-react-native/round-filled-radius-1-stroke-1
A collection of round filled React icons with 1px 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:IconRobotHeadSlop/index.js | AI (source-diff): Bundled SVG icon component from tsup; only requires react and react-native-svg. | ai | |
| source-diff | obfuscated-file:IconJson/index.js | AI (source-diff): Bundled SVG icon component from tsup; only requires react and react-native-svg. | ai | |
| source-diff | obfuscated-file:IconRust/index.js | AI (source-diff): Bundled SVG icon component from tsup; only requires react and react-native-svg. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library adding new icon components in bulk; expected growth pattern. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.js | AI (source-diff): Minified React Native SVG icon bundle; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSettingsGear4/index.mjs | AI (source-diff): Same pattern as .js counterpart; standard ESM icon bundle output. | ai | |
| source-diff | obfuscated-file:IconReact/index.mjs | AI (source-diff): tsup/esbuild minified ESM SVG icon component; same build pattern. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): tsup-bundled SVG icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.mjs | AI (source-diff): tsup-bundled SVG icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.js | AI (source-diff): tsup-bundled SVG icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconGraduateCap2/index.js | AI (source-diff): tsup-bundled SVG icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): tsup-bundled SVG icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSendLater/index.js | AI (source-diff): tsup-bundled SVG icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSunHigh/index.js | AI (source-diff): tsup-bundled SVG icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSunLow/index.js | AI (source-diff): tsup-bundled SVG icon component; long lines are SVG path data, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.js | AI (source-diff): Minified tsup/esbuild bundle output for SVG icon components; stable pattern across all versions of this icon library. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License-check script is consistent with commercial icon library pattern; no network or shell exec involved. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 1 / 5 | |
| 1.1.232 | 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.219 | 1 / 5 | |
| 1.1.218 | 1 / 5 | |
| 1.1.217 | 1 / 5 | |
| 1.1.216 | 1 / 5 | |
| 1.1.211 | 1 / 5 | |
| 1.1.196 | 1 / 5 | |
| 1.1.195 | 1 / 5 | |
| 1.1.194 | 1 / 5 | |
| 1.1.179 | 1 / 5 | |
| 1.1.178 | 1 / 5 | |
| 1.1.177 | 1 / 5 | |
| 1.1.176 | 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.232
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.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.211
12 findingsThis version was published by a different npm account than previous versions on 2026-04-24. This could indicate a legitimate maintainer transition or an account compromise.
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.
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.
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.196
10 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.
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.195
10 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.
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.194
9 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.
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.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.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.