Case file No.262 · pypi · stdio

DocSlicer

io.github.DocSlicer/docslicer · v0.2.5

Answer questions from documents too large to fit in context, reading only the sections you need.

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 52 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

164 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.2.5)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 DocSlicer safe?

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

Does DocSlicer have known CVEs or vulnerabilities?

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

When was DocSlicer last updated?

The latest registry version is 0.2.5, published Sep 1, 2026. The last push to DocSlicer/DocSlicer was on Sep 1, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does DocSlicer use?

GitHub reports the license of DocSlicer/DocSlicer as AGPL-3.0.

Related servers

same publisher / similar score