@hh.ru/magritte-ui-nav-bar
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:nav-bar-Bgo6GHaL.js | AI (source-diff): Long lines are CSS-modules class-name maps, a normal build artifact for this UI component package. | ai | |
| source-diff | obfuscated-file:NavBar-Cp0mcX9W.js | AI (source-diff): Standard minified React bundle output from hhru's magritte-ui monorepo; long lines are CSS module maps, not obfuscation. | ai | |
| source-diff | obfuscated-file:NavBar-C--dTXkW.js | AI (source-diff): Standard minified bundle output from the hh.ru Magritte UI design system; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:NavBar-OLh6N6lb.js | AI (source-diff): Standard bundled React component output; long lines are CSS module maps, not obfuscation. Stable pattern for this package family. | ai | |
| source-diff | obfuscated-file:nav-bar-CmjjkPy6.js | AI (source-diff): Long lines are CSS-modules class-name maps (bundled output), not obfuscated malicious code; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:NavBar-CCOJAysj.js | AI (source-diff): Standard minified build output for a UI component library; long lines are CSS module maps and bundled JSX, not obfuscation. | ai | |
| source-diff | obfuscated-file:NavBar-W-hjbnPP.js | AI (source-diff): Minified build artifact from hh.ru design system; content is readable React component code, not obfuscation. | ai | |
| source-diff | obfuscated-file:NavBar-wOJMPkNM.js | AI (source-diff): Standard minified build artifact from a UI component library; long lines are CSS module maps, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org design tokens dep; likely consumed via CSS/token files rather than direct JS import. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across the @hh.ru/magritte-ui package family; not a spam indicator here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo UI component; missing metadata is expected for org-scoped packages in this family. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.3.28 | 12 / 0 | |
| 1.3.26 | 10 / 0 | |
| 1.3.24 | 8 / 0 | |
| 1.3.22 | 8 / 0 | |
| 1.3.21 | 8 / 0 | |
| 1.3.20 | 8 / 0 | |
| 1.3.19 | 8 / 0 | |
| 1.3.18 | 8 / 0 | |
| 1.3.17 | 8 / 0 | |
| 1.3.16 | 8 / 0 | |
| 1.3.15 | 8 / 0 | |
| 1.3.14 | 8 / 0 | |
| 1.3.12 | 8 / 0 | |
| 1.3.11 | 8 / 0 | |
| 1.3.10 | 8 / 0 | |
| 1.3.9 | 8 / 0 | |
| 1.3.8 | 8 / 0 | |
| 1.3.7 | 8 / 0 | |
| 1.3.5 | 8 / 0 | |
| 1.3.4 | 8 / 0 | |
| 1.3.1 | 8 / 0 | |
| 1.3.0 | 8 / 0 | |
| 1.2.2 | 8 / 0 | |
| 1.1.28 | 8 / 0 | |
| 1.1.27 | 8 / 0 | |
| 1.1.26 | 8 / 0 | |
| 1.1.25 | 8 / 0 | |
| 1.1.24 | 8 / 0 | |
| 1.1.20 | 8 / 0 | |
| 1.1.18 | 8 / 0 | |
| 1.1.17 | 8 / 0 | |
| 1.1.15 | 8 / 0 | |
| 1.1.14 | 8 / 0 | |
| 1.1.13 | 8 / 0 | |
| 1.1.12 | 8 / 0 | |
| 1.1.11 | 8 / 0 | |
| 1.1.9 | 8 / 0 | |
| 1.1.8 | 8 / 0 | |
| 1.1.7 | 8 / 0 | |
| 1.1.6 | 8 / 0 | |
| 1.1.5 | 8 / 0 | |
| 1.1.4 | 8 / 0 | |
| 1.1.2 | 8 / 0 | |
| 1.1.1 | 8 / 0 | |
| 1.1.0 | 8 / 0 | |
| 1.0.2 | 6 / 0 | |
| 1.0.1 | 6 / 0 |
v1.3.28
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.3.26
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.3.24
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.3.22
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.3.21
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.3.20
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.3.19
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.3.18
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.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.