@central-icons-react/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 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:IconSvelte/index.js | AI (source-diff): Minified tsup/esbuild output of SVG icon component; not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:IconSendLater/index.js | AI (source-diff): Minified tsup/esbuild output of SVG icon component; not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): Minified tsup/esbuild output of SVG icon component; not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:IconGraduateCap2/index.js | AI (source-diff): Minified tsup/esbuild output of SVG icon component; not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): Minified tsup/esbuild CJS bundle for SVG icon component; pattern is consistent across all icon files in this library. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.mjs | AI (source-diff): Minified tsup/esbuild output with SVG path data; standard for this icon library. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.js | AI (source-diff): Minified tsup/esbuild output with SVG path data; standard for this icon library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files per release; large file counts are expected for this package. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): Minified tsup/esbuild ESM bundle of a React SVG icon component; no malicious code present. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Minified tsup/esbuild bundle of a React SVG icon component; no malicious code present. | ai | |
| source-diff | obfuscated-file:IconImagineHead/index.js | AI (source-diff): Minified tsup/esbuild bundle of a React SVG icon component; no malicious code present. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Runs local license-check.js only; consistent commercial license enforcement across all versions of this icon package family. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 0 / 5 | |
| 1.1.233 | 0 / 5 | |
| 1.1.231 | 0 / 5 | |
| 1.1.230 | 0 / 5 | |
| 1.1.229 | 0 / 5 | |
| 1.1.228 | 0 / 5 | |
| 1.1.226 | 0 / 5 | |
| 1.1.225 | 0 / 5 | |
| 1.1.224 | 0 / 5 | |
| 1.1.223 | 0 / 5 | |
| 1.1.220 | 0 / 5 | |
| 1.1.219 | 0 / 5 | |
| 1.1.218 | 0 / 5 | |
| 1.1.216 | 0 / 5 | |
| 1.1.197 | 0 / 5 | |
| 1.1.192 | 0 / 5 | |
| 1.1.190 | 0 / 5 | |
| 1.1.189 | 0 / 5 | |
| 1.1.186 | 0 / 5 | |
| 1.1.176 | 0 / 5 | |
| 1.1.175 | 0 / 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.233
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.231
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.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.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.197
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.192
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.190
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.189
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.186
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.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.