@central-icons-react/square-outlined-radius-0-stroke-1
A collection of square outlined 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:IconReact/index.mjs | AI (source-diff): ESM variant of the same bundled icon component; benign minification. | ai | |
| source-diff | obfuscated-file:IconBitcoinCircle/index.js | AI (source-diff): Minified tsup/esbuild output for SVG icon components; consistent pattern across all versions of this icon library. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): tsup/esbuild minified React icon component; SVG path data causes long lines, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconRust/index.js | AI (source-diff): tsup/esbuild minified React icon component; SVG path data causes long lines, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): tsup/esbuild minified React icon component; SVG path data causes long lines, not obfuscation. | ai | |
| source-diff | obfuscated-file:IconJson/index.js | AI (source-diff): tsup/esbuild minified React icon component; SVG path data causes long lines, not obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files across versions; large file additions are expected and benign. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License enforcement script (license-check.js) is a stable pattern for this commercial icon package family. | ai |
Versions (showing 30 of 30)
| 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.227 | 0 / 5 | |
| 1.1.225 | 0 / 5 | |
| 1.1.224 | 0 / 5 | |
| 1.1.223 | 0 / 5 | |
| 1.1.222 | 0 / 5 | |
| 1.1.221 | 0 / 5 | |
| 1.1.220 | 0 / 5 | |
| 1.1.219 | 0 / 5 | |
| 1.1.218 | 0 / 5 | |
| 1.1.217 | 0 / 5 | |
| 1.1.216 | 0 / 5 | |
| 1.1.198 | 0 / 5 | |
| 1.1.195 | 0 / 5 | |
| 1.1.193 | 0 / 5 | |
| 1.1.192 | 0 / 5 | |
| 1.1.189 | 0 / 5 | |
| 1.1.186 | 0 / 5 | |
| 1.1.182 | 0 / 5 | |
| 1.1.181 | 0 / 5 | |
| 1.1.180 | 0 / 5 | |
| 1.1.178 | 0 / 5 | |
| 1.1.177 | 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.227
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.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.198
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.195
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.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.178
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.
v1.1.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.