@hh.ru/magritte-ui-phone-input
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing metadata is consistent across all @hh.ru/magritte-* packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across the entire @hh.ru/magritte-* monorepo; not a malware indicator. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org monorepo dep; likely used transitively or via CSS imports not detected by static analysis. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-typography | AI (phantom-deps): Same-org monorepo dep; likely used transitively or via CSS imports not detected by static analysis. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.2.58 | 13 / 0 | |
| 4.2.57 | 13 / 0 | |
| 4.2.56 | 13 / 0 | |
| 4.2.55 | 13 / 0 | |
| 4.2.54 | 13 / 0 | |
| 4.2.53 | 13 / 0 | |
| 4.2.52 | 13 / 0 | |
| 4.2.51 | 13 / 0 | |
| 4.2.50 | 13 / 0 | |
| 4.2.16 | 13 / 0 | |
| 4.0.2 | 13 / 0 |
v4.2.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.