@hh.ru/magritte-ui-tree-selector
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@hh.ru/magritte-types | AI (dependencies): Same-org @hh.ru/* package from established publisher hhru; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-ui-card | AI (dependencies): Same-org @hh.ru/* package from established publisher hhru; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-ui-checkable-card | AI (dependencies): Same-org @hh.ru/* package from established publisher hhru; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-common-resize | AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of hh.ru's internal Magritte UI monorepo; missing metadata is consistent across all packages in this suite. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org sibling dep; likely used via CSS tokens; stable false positive. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across all @hh.ru/magritte-* packages; not a spam indicator here. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-spacing | AI (phantom-deps): Same-org sibling dep; likely used transitively or via CSS; stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.5.35 | 21 / 0 | |
| 5.5.34 | 21 / 0 | |
| 5.5.10 | 21 / 0 | |
| 5.2.6 | 21 / 0 | |
| 5.2.1 | 21 / 0 |
v5.5.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.