@hh.ru/magritte-ui-title
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Same-org monorepo internal dep; consistent with hhru's established component library pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal design system component; missing metadata is a monorepo publishing artifact, not a spam/malware signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all @hh.ru/magritte-* packages; monorepo artifact. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org design token dep; likely used via CSS/type imports not caught by static import analysis. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 8.1.7 | 6 / 0 | |
| 8.1.6 | 6 / 0 | |
| 8.1.5 | 5 / 0 | |
| 8.1.4 | 5 / 0 | |
| 8.1.3 | 5 / 0 | |
| 8.1.2 | 5 / 0 | |
| 8.1.1 | 5 / 0 | |
| 8.1.0 | 5 / 0 | |
| 8.0.3 | 5 / 0 | |
| 8.0.2 | 5 / 0 | |
| 8.0.1 | 5 / 0 | |
| 8.0.0 | 5 / 0 | |
| 7.0.33 | 5 / 0 | |
| 7.0.32 | 5 / 0 | |
| 7.0.31 | 5 / 0 | |
| 7.0.30 | 5 / 0 | |
| 7.0.29 | 5 / 0 | |
| 7.0.28 | 5 / 0 | |
| 7.0.27 | 5 / 0 | |
| 7.0.26 | 5 / 0 | |
| 7.0.25 | 5 / 0 | |
| 7.0.24 | 5 / 0 | |
| 7.0.23 | 5 / 0 | |
| 7.0.22 | 5 / 0 | |
| 7.0.21 | 5 / 0 | |
| 7.0.20 | 5 / 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 | |
| 7.0.13 | 5 / 0 |
v8.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.20
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. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.