@hh.ru/magritte-ui-action-list
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): Entire @hh.ru/magritte-ui monorepo family omits descriptions; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): No-description/no-repo pattern is consistent across the magritte-ui monorepo; not indicative of spam. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-button | AI (phantom-deps): Same-org monorepo component; phantom-dep is a stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-breakpoint | AI (phantom-deps): Same-org monorepo component; phantom-dep is a stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-internal-drop-base | AI (phantom-deps): Same-org monorepo component; phantom-dep is a stable false positive for this package family. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 8.1.56 | 9 / 0 | |
| 8.1.54 | 9 / 0 | |
| 8.1.28 | 8 / 0 | |
| 8.1.27 | 8 / 0 | |
| 8.1.23 | 8 / 0 | |
| 8.0.5 | 8 / 0 |
v8.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.