@hh.ru/magritte-ui-branded-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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance across all hh.ru packages; org-wide pattern, not a risk signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all hh.ru/magritte packages; org packaging pattern, not a malware indicator. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-types | AI (dependencies): Same org scope (@hh.ru); internal dependency from a well-established publisher with 273 approved packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Trusted org publisher with clean track record; no material changes vs prior approved version. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo component; missing metadata is expected for org-scoped packages in this family. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-breakpoint | AI (phantom-deps): Same-org dep; likely consumed transitively; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org dep; likely consumed transitively or via CSS; stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.3.7 | 8 / 0 | |
| 2.3.6 | 8 / 0 | |
| 2.3.4 | 8 / 0 | |
| 2.3.3 | 8 / 0 | |
| 2.1.73 | 8 / 0 | |
| 2.1.63 | 8 / 0 | |
| 2.1.62 | 8 / 0 | |
| 2.1.44 | 9 / 0 | |
| 2.1.33 | 9 / 0 | |
| 2.1.32 | 9 / 0 | |
| 2.1.31 | 9 / 0 | |
| 2.1.30 | 9 / 0 |
v2.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.