Case file No.270 · npm · stdio

q-ring

io.github.I4cTime/q-ring · v0.18.0

OS keychain secrets for AI coding agents, over MCP.

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

Source transparency15/15

public repo, license AGPL-3.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

159 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.18.0)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 q-ring safe?

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

Does q-ring have known CVEs or vulnerabilities?

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

When was q-ring last updated?

The latest registry version is 0.18.0, published Sep 27, 2026. The last push to I4cTime/q-ring was on Oct 22, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does q-ring use?

GitHub reports the license of I4cTime/q-ring as AGPL-3.0.

Related servers

same publisher / similar score