Case file No.277 · pypi · stdio

crapkit

io.github.JeanFrancoisGagne/crapkit · v0.8.1

Twelve tools to inspect CRAP scores, find work, and check edited functions against their ceiling.

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

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

447 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.8.1)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 crapkit safe?

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

Does crapkit have known CVEs or vulnerabilities?

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

When was crapkit last updated?

The latest registry version is 0.8.1, published Oct 1, 2026. The last push to JeanFrancoisGagne/crapkit was on Oct 6, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does crapkit use?

GitHub reports the license of JeanFrancoisGagne/crapkit as MIT.

Related servers

same publisher / similar score