@hh.ru/magritte-ui-snackbar
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo component package; missing metadata is expected for internal packages. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-common-resize | AI (phantom-deps): Same-org monorepo dep; may be used transitively or via CSS; stable false positive. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org monorepo dep; design tokens often consumed via CSS imports not caught by static analysis. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-typography | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-common-func-utils | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-internal-layer-name | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 6.3.19 | 14 / 1 | |
| 6.3.18 | 14 / 1 | |
| 6.3.17 | 14 / 1 | |
| 6.3.16 | 14 / 1 | |
| 6.3.15 | 14 / 1 | |
| 6.3.14 | 14 / 1 | |
| 6.3.13 | 14 / 1 | |
| 6.3.12 | 14 / 1 | |
| 6.3.11 | 14 / 1 | |
| 6.3.10 | 14 / 1 | |
| 6.3.9 | 14 / 1 | |
| 6.3.8 | 14 / 1 | |
| 6.3.7 | 14 / 1 | |
| 6.3.6 | 14 / 1 | |
| 6.3.5 | 14 / 1 | |
| 6.3.4 | 14 / 1 | |
| 6.3.3 | 14 / 1 | |
| 6.3.2 | 14 / 1 | |
| 6.3.1 | 14 / 1 | |
| 6.3.0 | 14 / 1 | |
| 6.2.11 | 14 / 1 | |
| 6.2.10 | 14 / 1 | |
| 6.2.9 | 14 / 1 | |
| 6.2.8 | 14 / 1 | |
| 6.2.7 | 14 / 1 | |
| 6.2.6 | 14 / 1 | |
| 6.2.5 | 14 / 1 | |
| 6.2.4 | 14 / 1 | |
| 6.2.3 | 14 / 1 | |
| 6.2.2 | 14 / 1 | |
| 6.2.1 | 14 / 1 | |
| 6.2.0 | 14 / 1 | |
| 6.1.35 | 14 / 1 | |
| 6.1.34 | 14 / 1 | |
| 6.1.33 | 14 / 1 | |
| 6.1.32 | 14 / 1 | |
| 6.1.31 | 14 / 1 | |
| 6.1.30 | 14 / 1 | |
| 6.1.29 | 14 / 1 | |
| 6.1.28 | 14 / 1 | |
| 6.1.27 | 14 / 1 | |
| 6.1.26 | 14 / 1 | |
| 6.1.25 | 14 / 1 | |
| 6.1.24 | 14 / 1 | |
| 6.1.23 | 14 / 1 | |
| 6.1.22 | 14 / 1 | |
| 6.1.21 | 14 / 1 | |
| 6.1.20 | 14 / 1 | |
| 6.1.19 | 14 / 1 | |
| 6.1.18 | 14 / 1 | |
| 6.1.17 | 14 / 1 |
v6.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.