Run local prompt regression checks from prompt-response logs in AI coding assistants.
Catch prompt regressions before they ship. Automatic eval suites from the prompt logs you already have. redline turns real prompt-response logs into local regression tests. It selects representative cases, replays your changed prompt, and shows the behavioral diff before a bad prompt reaches users. Run the public proof: The demo catches ten synthetic regressions without API keys, private logs, a…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Catch prompt regressions before they ship. Automatic eval suites from the prompt logs you already have. redline turns real prompt-response logs into local regression tests. It selects representative cases, replays your changed prompt, and shows the behavioral diff before a bad prompt reaches users. Run the public proof: The demo catches ten synthetic regressions without API keys, private logs, a cloud account, or an LLM judge. It writes JSON, Markdown, and self-contained Open the local demo…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.