@hh.ru/magritte-ui-breadcrumbs
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): Consistent across all hhru/magritte packages; org does not use Sigstore attestation. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-ui-card | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-types | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-ui-link | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-ui-bottom-sheet | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org design token dep; likely imported transitively or via CSS, not a phantom dep concern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across all @hh.ru/magritte-* monorepo packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing metadata is consistent across all @hh.ru/magritte-* packages, not a malice indicator. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 7.1.54 | 11 / 0 | |
| 7.1.53 | 11 / 0 | |
| 7.1.48 | 11 / 0 | |
| 7.1.44 | 11 / 0 | |
| 7.1.43 | 11 / 0 | |
| 7.1.39 | 11 / 0 | |
| 7.1.38 | 11 / 0 | |
| 7.1.36 | 11 / 0 | |
| 7.1.35 | 11 / 0 | |
| 7.1.31 | 11 / 0 | |
| 7.1.27 | 11 / 0 | |
| 7.1.26 | 11 / 0 | |
| 7.1.23 | 11 / 0 | |
| 7.1.19 | 11 / 0 | |
| 7.1.18 | 11 / 0 | |
| 7.1.16 | 11 / 0 | |
| 7.1.13 | 11 / 0 | |
| 7.1.12 | 11 / 0 | |
| 7.1.8 | 11 / 0 | |
| 7.1.4 | 11 / 0 | |
| 7.1.1 | 11 / 0 | |
| 7.1.0 | 11 / 0 | |
| 7.0.64 | 11 / 0 | |
| 7.0.63 | 11 / 0 | |
| 7.0.56 | 11 / 0 | |
| 7.0.54 | 11 / 0 | |
| 7.0.52 | 11 / 0 | |
| 7.0.50 | 11 / 0 | |
| 7.0.49 | 11 / 0 | |
| 7.0.47 | 11 / 0 | |
| 7.0.45 | 11 / 0 | |
| 7.0.43 | 11 / 0 | |
| 7.0.42 | 11 / 0 | |
| 7.0.38 | 11 / 0 | |
| 7.0.34 | 11 / 0 | |
| 7.0.33 | 11 / 0 | |
| 7.0.29 | 11 / 0 | |
| 7.0.28 | 11 / 0 | |
| 7.0.27 | 11 / 0 | |
| 7.0.23 | 11 / 0 | |
| 7.0.22 | 11 / 0 | |
| 7.0.19 | 11 / 0 | |
| 7.0.15 | 11 / 0 | |
| 7.0.13 | 11 / 0 | |
| 7.0.12 | 11 / 0 | |
| 7.0.11 | 11 / 0 | |
| 7.0.10 | 11 / 0 | |
| 7.0.9 | 11 / 0 | |
| 7.0.8 | 11 / 0 | |
| 7.0.5 | 11 / 0 | |
| 7.0.4 | 11 / 0 |
v7.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.18
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.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.8
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.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.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.15
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.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.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.