@hh.ru/magritte-ui-action-bar
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): New dep is same-org @hh.ru scope; consistent with the package's established pattern of intra-monorepo dependencies. | ai | |
| dependencies | unvetted-dep:@hh.ru/magritte-types | AI (dependencies): Same-org scoped package within the hhru/magritte design system; consistent with the rest of the dependency tree. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-ui-grid | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-types | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-design-tokens | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@hh.ru/magritte-internal-layer-name | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with all other @hh.ru/magritte-* component packages; not a spam indicator here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing description/repo/keywords is consistent across the entire @hh.ru/magritte-* family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present to compound this. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 5.3.28 | 13 / 0 | |
| 5.3.20 | 12 / 0 | |
| 5.3.15 | 12 / 0 | |
| 5.3.14 | 12 / 0 | |
| 5.3.13 | 12 / 0 | |
| 5.3.10 | 12 / 0 | |
| 5.3.9 | 12 / 0 | |
| 5.3.7 | 12 / 0 | |
| 5.3.6 | 12 / 0 | |
| 5.3.5 | 12 / 0 | |
| 5.3.2 | 12 / 0 | |
| 5.3.1 | 12 / 0 | |
| 5.1.5 | 12 / 0 | |
| 5.1.0 | 12 / 0 | |
| 5.0.29 | 11 / 0 | |
| 5.0.28 | 11 / 0 | |
| 5.0.22 | 11 / 0 | |
| 5.0.20 | 11 / 0 | |
| 5.0.19 | 11 / 0 | |
| 5.0.18 | 11 / 0 | |
| 5.0.15 | 11 / 0 | |
| 5.0.14 | 11 / 0 | |
| 5.0.11 | 11 / 0 | |
| 5.0.10 | 11 / 0 | |
| 5.0.8 | 11 / 0 | |
| 5.0.5 | 11 / 0 | |
| 5.0.4 | 11 / 0 | |
| 5.0.1 | 11 / 0 | |
| 5.0.0 | 11 / 0 |
v5.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.