Case file No.294 · pypi · stdio

io.github.yiminspace/quarry

io.github.yiminspace/quarry · v1.10.0

Safety-railed database access: Postgres, MySQL, SQLite, Redis. Read-only by default.

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

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

424 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

v1.9.0 → v1.10.0Oct 19, 2026
- version changed version bump
```
"1.9.0" → "1.10.0"
```
- packages.0.version changed package version bump
```
"1.9.0" → "1.10.0"
```
First snapshot (v1.9.0)Oct 18, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is io.github.yiminspace/quarry safe?

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

Does io.github.yiminspace/quarry have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package quarry-db. That is not proof of safety.

When was io.github.yiminspace/quarry last updated?

The latest registry version is 1.10.0, published Oct 18, 2026. The last push to yiminspace/quarry was on Oct 20, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does io.github.yiminspace/quarry use?

GitHub reports the license of yiminspace/quarry as MIT.

Related servers

same publisher / similar score