@ilo-org/react
React components for the ILO's Design System
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:lib/cjs/_store/AudioPlayer-chunk-Bl8nTWNa.js | AI (source-diff): Standard Vite/Rollup minified chunk; readable React component logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:lib/cjs/_store/CardGroup-chunk-C-uazBgd.js | AI (source-diff): Standard Vite/Rollup minified chunk; readable React component logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:lib/cjs/_store/Collapse-chunk-DWfNjmDa.js | AI (source-diff): Standard Vite/Rollup minified chunk; readable React component logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:lib/cjs/_store/components-entry-BBIoGeTD.js | AI (source-diff): Standard Vite/Rollup minified entry chunk; barrel re-exports of known components, no malicious patterns. | ai | |
| phantom-deps | phantom-dep:dom-helpers | AI (phantom-deps): Same bundled-output false positive pattern. | ai | |
| phantom-deps | phantom-dep:@ilo-org/fonts | AI (phantom-deps): Same-org scoped package; bundled output false positive. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Same bundled-output false positive pattern. | ai | |
| phantom-deps | phantom-dep:@ilo-org/styles | AI (phantom-deps): Same-org scoped package; bundled output false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires inside bundled video.js chunk; standard atob/Buffer base64 decode for binary data, not obfuscated payload. | ai | |
| phantom-deps | phantom-dep:@ilo-org/icons-react | AI (phantom-deps): Same-org scoped package; bundled output false positive. | ai | |
| phantom-deps | phantom-dep:@ilo-org/brand-assets | AI (phantom-deps): Same-org scoped package; bundled output false positive. | ai | |
| phantom-deps | phantom-dep:react-transition-group | AI (phantom-deps): Same bundled-output false positive pattern. | ai | |
| phantom-deps | phantom-dep:videojs-youtube | AI (phantom-deps): Same bundled-output false positive pattern. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Bundled output inlines imports; phantom-dep heuristic is a false positive for this build pattern. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Same bundled-output false positive pattern. | ai | |
| phantom-deps | phantom-dep:merge-refs | AI (phantom-deps): Same bundled-output false positive pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 14 / 38 | |
| 1.0.0 | 14 / 38 | |
| 0.28.8 | 14 / 38 | |
| 0.28.4 | 14 / 37 | |
| 0.28.1 | 14 / 37 | |
| 0.28.0 | 14 / 37 |
v1.1.0
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.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.