← Home

@meetploy/cli

npm Repository Homepage

The Ploy CLI for local development, type generation, and building workers with Cloudflare-compatible D1 and KV bindings.

9
Versions
SEE LICENSE IN ../../LICENSE
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

steebchen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:joi AI (typosquat): @meetploy/cli is a scoped CLI package with no relation to joi; Levenshtein match is coincidental. ai
phantom-deps phantom-dep:workerd AI (phantom-deps): workerd is the Cloudflare Workers runtime binary, an expected implicit dependency of wrangler. ai
phantom-deps phantom-dep:wrangler AI (phantom-deps): wrangler is referenced in config files as documented; not a phantom dep concern for this CLI package. ai

Versions (showing 9 of 9)

Version Deps Published
1.33.0 8 / 5
1.32.0 8 / 5
1.31.1 8 / 5
1.31.0 8 / 5
1.4.0 2 / 0
1.3.0 2 / 0
1.2.0 2 / 0
1.1.0 2 / 0
1.0.6 1 / 0

v1.33.0

1 finding
LOW No provenance attestation provenance

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

v1.32.0

1 finding
LOW No provenance attestation provenance

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

v1.31.1

1 finding
LOW No provenance attestation provenance

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

v1.31.0

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.

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

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.

v1.0.6

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.