@hh.ru/magritte-ui-avatar
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:Skeleton-DsxP08pw.js | AI (source-diff): Standard minified bundle output for a React UI component; long lines are CSS module maps, not obfuscation. | ai | |
| source-diff | obfuscated-file:Skeleton-vr-Papn9.js | AI (source-diff): Long lines are CSS-modules class-name maps in a bundled UI component; not obfuscation. | ai | |
| source-diff | obfuscated-file:Skeleton-CnWUvf8H.js | AI (source-diff): Minified CSS-modules bundle from a UI component library; pattern is stable across all versions of this package. | ai | |
| source-diff | obfuscated-file:Skeleton-LFTA_u5l.js | AI (source-diff): Long lines are CSS-modules class-name maps in a bundled UI component; standard build output for this package family. | ai | |
| source-diff | obfuscated-file:Skeleton-C0p3tV5v.js | AI (source-diff): Long lines are CSS-modules style maps in a bundled UI component — standard build output for this package family. | ai | |
| source-diff | obfuscated-file:Skeleton-BIMqxFjZ.js | AI (source-diff): Standard bundled React/CSS-modules output; long lines are CSS class name maps, not obfuscation. | ai | |
| source-diff | obfuscated-file:Skeleton-ClGp_xw6.js | AI (source-diff): Long lines are CSS-module class-name maps in a bundled UI component, not obfuscation. Stable pattern for this package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; publisher has a clean track record across 18 approved packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo UI component; missing metadata is expected for scoped org packages, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this internal design-system package; not a risk signal. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 8.2.0 | 8 / 0 | |
| 8.1.9 | 7 / 0 | |
| 8.1.8 | 7 / 0 | |
| 8.1.7 | 7 / 0 | |
| 8.1.6 | 7 / 0 | |
| 8.1.5 | 7 / 0 | |
| 8.1.4 | 7 / 0 | |
| 8.1.3 | 7 / 0 | |
| 8.1.2 | 7 / 0 | |
| 8.1.1 | 7 / 0 | |
| 8.1.0 | 7 / 0 | |
| 8.0.20 | 6 / 0 | |
| 8.0.19 | 6 / 0 | |
| 8.0.18 | 6 / 0 | |
| 8.0.17 | 6 / 0 | |
| 8.0.16 | 6 / 0 | |
| 8.0.15 | 6 / 0 | |
| 8.0.14 | 6 / 0 | |
| 8.0.13 | 6 / 0 | |
| 8.0.12 | 6 / 0 | |
| 8.0.11 | 6 / 0 | |
| 8.0.10 | 6 / 0 | |
| 8.0.9 | 6 / 0 | |
| 8.0.8 | 6 / 0 | |
| 8.0.7 | 6 / 0 | |
| 8.0.6 | 6 / 0 | |
| 8.0.5 | 6 / 0 | |
| 8.0.4 | 6 / 0 | |
| 8.0.3 | 6 / 0 | |
| 8.0.2 | 6 / 0 | |
| 8.0.1 | 6 / 0 | |
| 8.0.0 | 6 / 0 |
v8.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.9
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.8
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.