Case file No.084 · pypi · stdio

subtask

io.github.tedin7/subtask · v0.4.5

Background sub-agents for Claude Code, Codex, Kimi and OpenCode, over MCP, with a spend cap.

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

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption6/10

1261 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.3.1 → v0.4.5Oct 19, 2026
- version changed version bump
```
"0.3.1" → "0.4.5"
```
- packages.0.version changed package version bump
```
"0.3.1" → "0.4.5"
```
First snapshot (v0.3.1)Oct 18, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is subtask safe?

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

Does subtask have known CVEs or vulnerabilities?

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

When was subtask last updated?

The latest registry version is 0.4.5, published Oct 19, 2026. The last push to tedin7/subtask was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does subtask use?

GitHub reports the license of tedin7/subtask as MIT.

Related servers

same publisher / similar score