@hh.ru/magritte-ui
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 | new-deps-added | AI (publish-pattern): New deps are all @hh.ru/magritte-ui-* sub-packages from the same org; consistent with normal monorepo component additions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Aggregator package in a large monorepo; missing description/repo/keywords is a known pattern for internal component bundles. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-fonts | AI (phantom-deps): Same-org CSS/font dep; likely re-exported or used indirectly via CSS imports not visible to static analysis. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-reset-css | AI (phantom-deps): Same-org CSS dep; phantom detection is a false positive for CSS-only packages. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org design tokens dep; likely consumed via CSS/SCSS imports not tracked by static analysis. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-translate-guard | AI (phantom-deps): Same-org dep; phantom detection false positive for this aggregator package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 138.6.2 | 91 / 0 | |
| 138.6.1 | 91 / 0 | |
| 138.5.0 | 91 / 0 | |
| 136.3.0 | 90 / 0 | |
| 128.6.0 | 87 / 0 |
v138.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v138.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v138.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v136.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v128.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.