Case file No.025 · pypi · stdio

doc-control

io.github.nuncaeslupus/doc-control · v0.10.1

Edit Word documents by address: tracked changes, comments, anchors, with backups and undo.

Package ↗GitHub ↗

Security score

96/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

Adoption6/10

3080 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

v0.9.0 → v0.10.1Oct 21, 2026
- version changed version bump
```
"0.9.0" → "0.10.1"
```
- packages.0.version changed package version bump
```
"0.9.0" → "0.10.1"
```
v0.8.4 → v0.9.0Oct 20, 2026
- version changed version bump
```
"0.8.4" → "0.9.0"
```
- packages.0.version changed package version bump
```
"0.8.4" → "0.9.0"
```
v0.8.3 → v0.8.4Oct 19, 2026
- version changed version bump
```
"0.8.3" → "0.8.4"
```
- packages.0.version changed package version bump
```
"0.8.3" → "0.8.4"
```
First snapshot (v0.8.3)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is doc-control safe?

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

Does doc-control have known CVEs or vulnerabilities?

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

When was doc-control last updated?

The latest registry version is 0.10.1, published Oct 20, 2026. The last push to nuncaeslupus/doc-control was on Oct 20, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does doc-control use?

GitHub reports the license of nuncaeslupus/doc-control as MIT.

Related servers

same publisher / similar score