← Case index
Case file No.115 · pypi · stdio
ChimeraForge
io.github.Sahil170595/chimeraforge · v0.66.0
Local-first LLM deployment planner: GPU/VRAM sizing, cost and latency, with provenance
Security score
93/100
Strong
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.devNo advisories found in OSV for this package name. (Not proof of safety.)
Metadata change timeline
rug-pull detection- v0.61.0 → v0.66.0Oct 18, 2026
versionchanged version bump"0.61.0" → "0.66.0"
packages.0.versionchanged package version bump"0.61.0" → "0.66.0"
packages.0.runtimeArguments.0.valuechanged version string inside argument"chimeraforge[mcp]==0.61.0" → "chimeraforge[mcp]==0.66.0"
- First snapshot (v0.61.0)Oct 16, 2026
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs ChimeraForge safe?
MCPWatch gives ChimeraForge a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.
Does ChimeraForge have known CVEs or vulnerabilities?
No advisories were found in OSV.dev for the pypi package chimeraforge. That is not proof of safety.
When was ChimeraForge last updated?
The latest registry version is 0.66.0, published Oct 18, 2026. The last push to Sahil170595/Chimeraforge was on Oct 20, 2026. MCPWatch last checked it on Oct 21, 2026.
What license does ChimeraForge use?
GitHub reports the license of Sahil170595/Chimeraforge as MIT.