Case file No.032 · pypi · stdio

io.github.aokings/thth

io.github.aokings/thth · v4.3.1

Call before you post: ships a draft to Threads/Bluesky/Mastodon only after a person approved it.

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

2618 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

v4.2.2 → v4.3.1Oct 20, 2026
- version changed version bump
```
"4.2.2" → "4.3.1"
```
- packages.0.version changed package version bump
```
"4.2.2" → "4.3.1"
```
v4.2.1 → v4.2.2Oct 19, 2026
- version changed version bump
```
"4.2.1" → "4.2.2"
```
- packages.0.version changed package version bump
```
"4.2.1" → "4.2.2"
```
First snapshot (v4.2.1)Oct 18, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is io.github.aokings/thth safe?

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

Does io.github.aokings/thth have known CVEs or vulnerabilities?

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

When was io.github.aokings/thth last updated?

The latest registry version is 4.3.1, published Oct 19, 2026. The last push to aokings/thth was on Oct 20, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does io.github.aokings/thth use?

GitHub reports the license of aokings/thth as MIT.

Related servers

same publisher / similar score