Case file No.305 · pypi · stdio

LLMScribe

io.github.AMRITO-KUNDU/llmscribe · v1.2.1

Deterministic repo map, search and file reader for AI agents.

Package ↗GitHub ↗

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 4 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

125 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 (v1.2.1)Oct 24, 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 LLMScribe safe?

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

Does LLMScribe have known CVEs or vulnerabilities?

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

When was LLMScribe last updated?

The latest registry version is 1.2.1, published Oct 13, 2026. The last push to AMRITO-KUNDU/llmscribe was on Oct 20, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does LLMScribe use?

GitHub reports the license of AMRITO-KUNDU/llmscribe as Apache-2.0.

Related servers

same publisher / similar score