Case file No.321 · pypi · stdio

digline

dev.digline/digline-mcp · v0.6.1

Read, measure and explain LLM eval runs of a digline suite. Cannot promote a baseline.

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

v0.5.0 → v0.6.1Oct 19, 2026
- version changed version bump
```
"0.5.0" → "0.6.1"
```
- packages.0.version changed package version bump
```
"0.5.0" → "0.6.1"
```
First snapshot (v0.5.0)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is digline safe?

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

Does digline have known CVEs or vulnerabilities?

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

When was digline last updated?

The latest registry version is 0.6.1, published Oct 19, 2026. The last push to digline/digline was on Oct 21, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does digline use?

GitHub reports the license of digline/digline as Apache-2.0.

Related servers

same publisher / similar score