@hh.ru/magritte-ui-cell
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 monorepo UI component; missing description is a stable pattern across this org's packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Trusted org publisher with 129 approved packages; dormancy pattern consistent with internal release cadence, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal UI component from established org; missing metadata is a style issue, not a malice indicator. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-breakpoint | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic likely misfires on this package's import patterns. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 7.2.19 | 10 / 0 | |
| 7.2.18 | 10 / 0 | |
| 7.2.17 | 10 / 0 | |
| 7.2.16 | 10 / 0 | |
| 7.2.15 | 10 / 0 | |
| 7.2.12 | 10 / 0 | |
| 7.2.9 | 10 / 0 | |
| 7.2.8 | 10 / 0 | |
| 7.2.4 | 10 / 0 | |
| 7.2.3 | 10 / 0 | |
| 7.2.2 | 10 / 0 | |
| 7.2.1 | 10 / 0 | |
| 7.2.0 | 10 / 0 | |
| 7.1.16 | 10 / 0 | |
| 7.1.11 | 10 / 0 | |
| 7.1.6 | 10 / 0 | |
| 7.1.1 | 10 / 0 | |
| 7.1.0 | 10 / 0 | |
| 7.0.14 | 10 / 0 | |
| 7.0.13 | 10 / 0 | |
| 7.0.11 | 10 / 0 | |
| 7.0.10 | 10 / 0 | |
| 7.0.7 | 10 / 0 | |
| 7.0.6 | 10 / 0 | |
| 7.0.4 | 10 / 0 | |
| 7.0.3 | 10 / 0 | |
| 7.0.0 | 10 / 0 |
v7.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.