← Home

@zkp2p/contracts-v2

ZKP2P V2 smart contract interfaces and utilities

16
Versions
MIT
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

0xsachinkrichardliangkartik4152prlabsdavyjonespeer

Keywords

zkp2pethereumsmart-contractsdefip2pfiatonrampofframp

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads local JSON config files by network name within the package directory — a standard config-loading pattern, not arbitrary module loading. ai

Versions (showing 16 of 16)

Version Deps Published
0.3.0 1 / 13
0.2.4 1 / 13
0.2.3 1 / 13
0.2.2 1 / 13
0.2.1 1 / 13
0.2.0 1 / 13
0.0.11 1 / 13
0.0.10 1 / 13
0.0.9 1 / 13
0.0.8 1 / 13
0.0.7 1 / 13
0.0.6 1 / 13
0.0.5 1 / 13
0.0.4 0 / 13
0.0.2 0 / 13
0.0.1 0 / 13

v0.3.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: 0xsachink → richardliang (on 2026-07-15, known maintainer) provenance

This version was published by a different npm account (richardliang) than the most recent previously approved version (0xsachink) on 2026-07-15, but richardliang is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.