Case file No.312 · pypi · stdio

keygrant

io.github.bazingaedward/keygrant · v0.1.9

Run commands with API keys injected per call — values never enter model context.

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

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

392 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.1.9)Oct 18, 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 keygrant safe?

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

Does keygrant have known CVEs or vulnerabilities?

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

When was keygrant last updated?

The latest registry version is 0.1.9, published Oct 17, 2026. The last push to bazingaedward/keygrant was on Oct 17, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does keygrant use?

GitHub reports the license of bazingaedward/keygrant as Apache-2.0.

Related servers

same publisher / similar score