@central-icons-react-native/square-filled-radius-0-stroke-1
A collection of square filled React icons with 0px 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 | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files across versions; large file additions are expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; no provenance attestation but consistent with all prior versions of this package. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Minified icon component bundle with readable SVG path data; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): Minified ESM icon component bundle; standard build output for this icon library. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License check script is a documented commercial license enforcement pattern for this icon library; stable across versions. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 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.216 | 1 / 5 | |
| 1.1.191 | 1 / 5 | |
| 1.1.184 | 1 / 5 | |
| 1.1.182 | 1 / 5 | |
| 1.1.177 | 1 / 5 | |
| 1.1.176 | 1 / 5 | |
| 1.1.175 | 1 / 5 |
v1.1.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.226
1 finding[Accepted risk] Package 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.191
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.184
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.182
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.