@hh.ru/magritte-ui-chips
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal org component; missing description is consistent across all hh.ru magritte packages. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org internal dep; phantom-dep heuristic fires on indirect/transitive usage patterns common in monorepos. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-breakpoint | AI (phantom-deps): Same-org internal dep; phantom-dep heuristic fires on indirect/transitive usage patterns common in monorepos. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-common-keyboard | AI (phantom-deps): Same-org internal dep; phantom-dep heuristic fires on indirect/transitive usage patterns common in monorepos. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo UI component; missing description/keywords/repo URL is typical for private org packages published to npm. | ai |
v7.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.