Case file No.239 · npm · stdio

Clize

ai.clize/clize · v0.52.0

Real-world actions for AI coding agents: an inbox with approval outbox, deploys, domains, payments.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 19 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

527 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v0.52.0)Oct 16, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Clize safe?

MCPWatch gives Clize a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does Clize have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the npm package @clize/clize. That is not proof of safety.

When was Clize last updated?

The latest registry version is 0.52.0, published Oct 12, 2026. The last push to cooldk/clize-cli was on Oct 1, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Clize use?

GitHub reports the license of cooldk/clize-cli as MIT.

Related servers

same publisher / similar score