Case file No.380 · pypi · stdio

Docpick

io.github.ArkNill/docpick · v0.1.2

Schema-driven document extraction with local OCR + LLM. Document in, Structured JSON out.

Package ↗GitHub ↗

Security score

83/100

Good

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance10/20

last push 192 days ago

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

285 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.1.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 above

Is Docpick safe?

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

Does Docpick have known CVEs or vulnerabilities?

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

When was Docpick last updated?

The latest registry version is 0.1.2, published Mar 17, 2026. The last push to QuartzUnit/docpick was on Apr 15, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does Docpick use?

GitHub reports the license of QuartzUnit/docpick as Apache-2.0.

Related servers

same publisher / similar score