@hh.ru/magritte-ui-banner
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @hh.ru scoped package; consistent with established publisher pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across hh.ru magritte-ui component packages; not a malware indicator. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org monorepo dep; may be used transitively or via CSS imports rather than direct JS import. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-breakpoint | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal UI component from established hhru monorepo; missing metadata is a known pattern for this org's packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 6.2.17 | 7 / 0 | |
| 6.1.18 | 6 / 0 | |
| 6.1.14 | 6 / 0 | |
| 6.1.4 | 6 / 0 | |
| 6.0.42 | 6 / 0 | |
| 6.0.26 | 6 / 0 | |
| 6.0.22 | 6 / 0 | |
| 6.0.20 | 6 / 0 | |
| 6.0.18 | 6 / 0 | |
| 6.0.10 | 6 / 0 | |
| 6.0.8 | 6 / 0 | |
| 6.0.6 | 6 / 0 | |
| 6.0.3 | 6 / 0 | |
| 6.0.2 | 6 / 0 | |
| 6.0.0 | 6 / 0 |
v6.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.