@hh.ru/magritte-ui-checkbox-radio
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal org package; no provenance is consistent across all hh.ru/magritte-* packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo UI component; missing metadata is consistent across all @hh.ru/magritte-* packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across this org's component packages; not a spam/malware indicator. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org design token dep; likely used via CSS/build pipeline rather than direct JS import. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-breakpoint | AI (phantom-deps): Same-org dep; phantom detection is a heuristic and may miss indirect usage patterns in this monorepo. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.1.10 | 7 / 0 | |
| 4.1.3 | 7 / 0 | |
| 4.1.2 | 7 / 0 | |
| 4.0.34 | 7 / 0 | |
| 4.0.33 | 7 / 0 | |
| 4.0.31 | 7 / 0 | |
| 4.0.26 | 7 / 0 | |
| 4.0.21 | 7 / 0 | |
| 4.0.20 | 7 / 0 | |
| 4.0.19 | 7 / 0 | |
| 4.0.14 | 7 / 0 | |
| 4.0.13 | 7 / 0 | |
| 4.0.7 | 7 / 0 | |
| 4.0.5 | 7 / 0 |
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.