@hh.ru/magritte-ui-skeleton
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 | dormant-publish | AI (publish-pattern): Publisher hhru has 114 approved packages and strong org-scoped ecosystem; dormancy is not indicative of takeover here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org UI component package; missing metadata is a style issue, not a spam/malware indicator for this publisher. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across hh.ru scoped packages; not a malice indicator for this org. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-types | AI (phantom-deps): Same-org type-only dep; phantom-dep false positive for type declaration packages. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org design tokens dep; likely used via CSS/type imports not caught by import scanner. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.0.21 | 3 / 0 | |
| 3.0.20 | 3 / 0 | |
| 3.0.19 | 3 / 0 | |
| 3.0.18 | 3 / 0 | |
| 3.0.16 | 3 / 0 | |
| 3.0.14 | 3 / 0 | |
| 3.0.13 | 3 / 0 | |
| 3.0.10 | 3 / 0 | |
| 3.0.9 | 3 / 0 | |
| 3.0.7 | 3 / 0 | |
| 3.0.5 | 3 / 0 | |
| 3.0.3 | 3 / 0 | |
| 3.0.2 | 3 / 0 | |
| 3.0.0 | 3 / 0 |
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.