@central-icons-react/square-filled-radius-0-stroke-1.5
A collection of square filled React icons with 0px radius and 1.5px 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:IconBitcoinCircle/index.js | AI (source-diff): Minified CJS bundle from tsup build; standard pattern for this icon library across all versions. | ai | |
| source-diff | obfuscated-file:IconJson/index.js | AI (source-diff): Minified React icon component; same bundler pattern as other icons in this package. | ai | |
| provenance | publisher-changed | AI (provenance): If confirmed legitimate CI/CD transition, this pattern will recur on every future version published via GitHub Actions. | ai | |
| source-diff | obfuscated-file:IconRobotHeadSlop/index.js | AI (source-diff): Minified React icon component; same bundler pattern as other icons in this package. | ai | |
| source-diff | obfuscated-file:IconRust/index.js | AI (source-diff): Minified React icon component; same bundler pattern as other icons in this package. | ai | |
| source-diff | obfuscated-file:IconReact/index.js | AI (source-diff): tsup-minified React SVG icon component; readable SVG paths visible in sample, no malicious code. | ai | |
| source-diff | obfuscated-file:IconReact/index.mjs | AI (source-diff): tsup-minified ESM React SVG icon component; same benign pattern as CJS counterpart. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.mjs | AI (source-diff): tsup-minified ESM React SVG icon component; same benign pattern as CJS counterpart. | ai | |
| source-diff | obfuscated-file:IconFullMoon/index.js | AI (source-diff): tsup-minified React SVG icon component; readable SVG paths visible in sample, no malicious code. | ai | |
| source-diff | obfuscated-file:IconSendLater/index.js | AI (source-diff): tsup-minified React SVG icon component; readable SVG paths visible in sample, no malicious code. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library adds batches of new icons per release; 90 new files is expected growth for this package. | ai | |
| source-diff | obfuscated-file:IconSvelte/index.js | AI (source-diff): tsup-minified React SVG icon component; readable SVG paths visible in sample, no malicious code. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.mjs | AI (source-diff): ESM variant of the same minified React SVG icon component; benign bundler output. | ai | |
| source-diff | obfuscated-file:IconMoon1/index.js | AI (source-diff): Minified React SVG icon component; no obfuscation, just bundler output with long SVG path strings. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): License check script only; consistent pattern across all versions of this icon library package family. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.1.234 | 0 / 5 | |
| 1.1.233 | 0 / 5 | |
| 1.1.232 | 0 / 5 | |
| 1.1.231 | 0 / 5 | |
| 1.1.230 | 0 / 5 | |
| 1.1.229 | 0 / 5 | |
| 1.1.228 | 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.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.197 | 0 / 5 | |
| 1.1.196 | 0 / 5 | |
| 1.1.181 | 0 / 5 | |
| 1.1.180 | 0 / 5 | |
| 1.1.177 | 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.232
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.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.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
8 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.
Package 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.196
7 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.181
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.180
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.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.