Case file No.215 · npm · stdio

Octri CLI

dev.octri/cli · v1.0.6

Push OpenAPI specs, build SDKs in ten languages, publish API docs, and triage production SDK errors.

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 12 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

202 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 (v1.0.6)Oct 24, 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 Octri CLI safe?

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

Does Octri CLI have known CVEs or vulnerabilities?

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

When was Octri CLI last updated?

The latest registry version is 1.0.6, published Oct 12, 2026. The last push to octridev/octri-cli was on Oct 12, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does Octri CLI use?

GitHub reports the license of octridev/octri-cli as MIT.

Related servers

same publisher / similar score