@hh.ru/magritte-internal-drop-base
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@hh.ru/magritte-ui-theme-wrapper | AI (dependencies): Same-org magritte design system dep; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-common-use-multiple-refs | AI (dependencies): Same-org magritte design system dep; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-common-use-when-font-loaded | AI (dependencies): Same-org magritte design system dep; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-common-mouse | AI (dependencies): Same-org magritte design system dep; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-common-use-no-bubbling | AI (dependencies): Same-org magritte design system dep; stable pattern across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with other Magritte internal packages; not a spam indicator here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal component of hh.ru Magritte design system; sparse metadata is consistent across the package family. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 7.2.8 | 6 / 0 | |
| 7.2.7 | 6 / 0 | |
| 7.2.6 | 6 / 0 | |
| 7.2.5 | 6 / 0 | |
| 7.2.4 | 6 / 0 | |
| 7.2.3 | 6 / 0 | |
| 7.2.2 | 6 / 0 | |
| 7.2.1 | 6 / 0 | |
| 7.2.0 | 6 / 0 | |
| 7.1.20 | 6 / 0 | |
| 7.1.19 | 6 / 0 | |
| 7.1.18 | 6 / 0 | |
| 7.1.17 | 6 / 0 | |
| 7.1.16 | 6 / 0 | |
| 7.1.15 | 6 / 0 | |
| 7.1.14 | 6 / 0 | |
| 7.1.13 | 6 / 0 | |
| 7.1.12 | 6 / 0 | |
| 7.1.11 | 6 / 0 | |
| 7.1.10 | 6 / 0 | |
| 7.1.9 | 6 / 0 | |
| 7.1.8 | 6 / 0 | |
| 7.1.7 | 6 / 0 | |
| 7.1.6 | 6 / 0 | |
| 7.1.5 | 6 / 0 | |
| 7.1.4 | 6 / 0 | |
| 7.1.3 | 6 / 0 | |
| 7.1.2 | 6 / 0 | |
| 7.1.1 | 6 / 0 | |
| 7.1.0 | 6 / 0 | |
| 7.0.19 | 5 / 0 | |
| 7.0.18 | 5 / 0 | |
| 7.0.17 | 5 / 0 | |
| 7.0.16 | 5 / 0 | |
| 7.0.15 | 5 / 0 | |
| 7.0.14 | 5 / 0 |
v7.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.6
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. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.