← Home

@mekari/pixel-popper

npm Repository Homepage
3
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, so a manually published version cannot be tied back to a reviewed commit.

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): Internal sibling package from same Mekari design-system monorepo; stable false positive. ai
dependencies unvetted-dep:@mekari/pixel-utils AI (dependencies): Internal sibling package from same Mekari design-system monorepo; stable false positive. ai
dependencies unvetted-dep:@mekari/pixel-portal AI (dependencies): Internal sibling package from same Mekari design-system monorepo; stable false positive. ai
dependencies unvetted-dep:@mekari/pixel-pseudo-box AI (dependencies): Internal sibling package from same Mekari design-system monorepo; stable false positive. ai

Versions (showing 3 of 3)

Version Deps Published
0.3.7 6 / 2
0.3.6 6 / 2
0.3.5 6 / 2

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

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.