@hh.ru/magritte-ui-button
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): Consistent across all hh.ru magritte packages; not a malice signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @hh.ru scope; consistent with internal UI library evolution. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org UI component; missing repo/keywords/description is a consistent pattern across this package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all hh.ru magritte packages; stable org pattern. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo component libraries. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-breakpoint | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo component libraries. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 7.2.4 | 8 / 0 | |
| 7.2.3 | 8 / 0 | |
| 7.2.1 | 8 / 0 | |
| 7.2.0 | 8 / 0 | |
| 7.1.10 | 7 / 0 | |
| 7.1.9 | 7 / 0 | |
| 7.1.7 | 7 / 0 | |
| 7.1.5 | 7 / 0 | |
| 7.1.4 | 7 / 0 | |
| 7.1.3 | 7 / 0 | |
| 7.1.2 | 7 / 0 | |
| 7.1.1 | 7 / 0 | |
| 7.1.0 | 7 / 0 | |
| 7.0.12 | 7 / 0 | |
| 7.0.11 | 7 / 0 | |
| 7.0.10 | 7 / 0 | |
| 7.0.9 | 7 / 0 | |
| 7.0.8 | 7 / 0 | |
| 7.0.6 | 7 / 0 | |
| 7.0.5 | 7 / 0 | |
| 7.0.4 | 7 / 0 | |
| 7.0.3 | 7 / 0 | |
| 7.0.1 | 7 / 0 | |
| 7.0.0 | 7 / 0 | |
| 6.0.24 | 7 / 0 | |
| 6.0.23 | 7 / 0 | |
| 6.0.22 | 7 / 0 | |
| 6.0.21 | 7 / 0 | |
| 6.0.20 | 7 / 0 | |
| 6.0.17 | 7 / 0 |
v7.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.2
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.12
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.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.8
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.5
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.1
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.
v6.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.