@hh.ru/magritte-ui-icon
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:IconDynamic-D7EOwIzl.js | AI (source-diff): Long lines are CSS-module class-name maps in a bundled React component — standard build output for this UI library. | ai | |
| source-diff | obfuscated-file:IconDynamic-BAC1U7QU.js | AI (source-diff): Minified React/CSS-module bundle output; consistent with this UI library's build process. | ai | |
| source-diff | obfuscated-file:IconDynamic-rcr7F4BX.js | AI (source-diff): Long lines are CSS-modules class-name maps in a bundled React component — normal build output for this UI library. | ai | |
| source-diff | obfuscated-file:IconDynamic-DdAJC3I0.js | AI (source-diff): Minified build artifact from hh.ru design system; no malicious patterns in sample. | ai | |
| source-diff | obfuscated-file:IconDynamic-CgSHDsLZ.js | AI (source-diff): Long lines are CSS-modules class-name maps in a bundled React component — standard build output for this UI library. | ai | |
| source-diff | obfuscated-file:IconDynamic-BspHwul0.js | AI (source-diff): Long lines are CSS-modules hashed class name maps in a standard UI library build bundle, not obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library; large file count increases are expected with new icon additions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party @hh.ru scoped package consistent with the magritte ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): hh.ru org packages consistently lack description/repo metadata; not indicative of malice. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across this publisher's packages; not a risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 14.2.9 | 9 / 3 | |
| 14.2.8 | 9 / 3 | |
| 14.2.7 | 8 / 3 | |
| 14.2.6 | 8 / 3 | |
| 14.2.5 | 8 / 3 | |
| 14.2.4 | 8 / 3 | |
| 14.2.3 | 8 / 3 | |
| 14.2.2 | 8 / 3 | |
| 14.2.1 | 8 / 3 | |
| 14.2.0 | 8 / 3 | |
| 14.1.0 | 8 / 3 | |
| 13.2.2 | 7 / 3 |
v14.2.9
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.
v14.2.8
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.
v14.2.7
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.
v14.2.6
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.
v14.2.5
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.
v14.2.4
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.
v14.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.