← Home

@hh.ru/magritte-ui-checkable-card

4
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

hhru

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Consistent across all hhru/magritte packages; monorepo convention. ai
provenance no-provenance AI (provenance): No provenance across all hhru packages; org-wide pattern, not a per-version concern. ai
bogus-package bogus-package AI (bogus-package): Internal monorepo component; missing metadata is expected for scoped org packages, not a spam indicator. ai
phantom-deps phantom-dep:@hh.ru/magritte-design-tokens AI (phantom-deps): Same org scope; likely used transitively or via CSS imports not detected by the heuristic. ai
phantom-deps phantom-dep:@hh.ru/magritte-ui-breakpoint AI (phantom-deps): Same org scope; phantom-dep heuristic unreliable for CSS/type-only imports in monorepo packages. ai

Versions (showing 4 of 4)

Version Deps Published
5.0.25 9 / 0
5.0.24 9 / 0
5.0.18 9 / 0
5.0.14 9 / 0

v5.0.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.24

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.