Case file No.473 · pypi · stdio

Flieber

com.flieber/flieber · v0.1.7

Your Flieber account in your AI assistant: sales, forecast, inventory, replenishment and more.

Package ↗Website ↗

Security score

73/100

Good

Normalized over 80 points of available evidence.

Unknown: Maintenance

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Source transparency0/15

no public GitHub repository linked

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

598 weekly downloads

Maintenanceunknown

Excluded from the score — no data available.

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.7)Oct 22, 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 Flieber safe?

MCPWatch gives Flieber a heuristic security score of 73/100 (good), based on 80 points of available evidence; unknown: Maintenance. This is an automated heuristic, not an audit.

Does Flieber have known CVEs or vulnerabilities?

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

When was Flieber last updated?

The latest registry version is 0.1.7, published Oct 22, 2026. The last repository push is unknown. MCPWatch last checked it on Oct 24, 2026.

What license does Flieber use?

Unknown — no public GitHub repository is linked in the registry.

Related servers

same publisher / similar score