← Case index
Case file No.299 · pypi · stdio
io.github.Wangggym/quarry
io.github.Wangggym/quarry · v0.2.2
Safety-railed database access for agents: Postgres, MySQL, Redis. Read-only by default.
Security score
93/100
Strong
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.devNo advisories found in OSV for this package name. (Not proof of safety.)
Metadata change timeline
rug-pull detection- First snapshot (v0.2.2)Oct 17, 2026
No changes observed yet across 1 snapshot(s).
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs io.github.Wangggym/quarry safe?
MCPWatch gives io.github.Wangggym/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.Wangggym/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.Wangggym/quarry last updated?
The latest registry version is 0.2.2, published Jul 2, 2026. The last push to Wangggym/quarry was on Oct 20, 2026. MCPWatch last checked it on Oct 21, 2026.
What license does io.github.Wangggym/quarry use?
GitHub reports the license of Wangggym/quarry as MIT.