← Home

@mekari/pixel-autocomplete

npm Repository Homepage

Mekari Pixel | Selecting items in a list from a text input component

6
Versions
LGPL-3.0
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

jochristiantomkrhelloerwin_mekariaryamekarimekaripackagesdrsuxezakiy_mekaridirgamekarisasmkr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@mekari/pixel-box AI (dependencies): Same-org sibling component; stable pattern across all @mekari/pixel-* packages. ai
dependencies unvetted-dep:@mekari/pixel-flex AI (dependencies): Same-org sibling component; stable pattern across all @mekari/pixel-* packages. ai
dependencies unvetted-dep:@mekari/pixel-text AI (dependencies): Same-org sibling component; stable pattern across all @mekari/pixel-* packages. ai
dependencies unvetted-dep:@mekari/pixel-utils AI (dependencies): Same-org sibling component; stable pattern across all @mekari/pixel-* packages. ai
dependencies unvetted-dep:@mekari/pixel-pseudo-box AI (dependencies): Same-org sibling component; stable pattern across all @mekari/pixel-* packages. ai
phantom-deps phantom-dep:@mekari/pixel-pseudo-box AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo component libraries. ai

Versions (showing 6 of 6)

Version Deps Published
0.14.47 10 / 1
0.14.46 10 / 1
0.14.45 10 / 1
0.14.44 10 / 1
0.14.43 10 / 1
0.14.42 10 / 1

v0.14.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.45

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.

v0.14.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.43

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.42

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.