io.github.panbanda/omen

MCPcommunity
v3.0.0io.github.panbandaUnknownUpdated 6mo agoGitHub

Multi-language code analysis for complexity, debt, hotspots, ownership, and defect prediction

Your AI writes code without knowing where the landmines are. Omen gives AI assistants the context they need: complexity hotspots, hidden dependencies, defect-prone files, and self-admitted debt. One command surfaces what's invisible. Why "Omen"? An omen is a sign of things to come - good or bad. Your codebase is full of omens: low complexity and clean architecture signal smooth sailing ahead,…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
6mo agoLast update
Package
Authorio.github.panbanda
LicenseUnknown
Version3.0.0
Sourcemcp-registry
GitHubpanbanda/omen
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—CVE scan · not run+0/30
→ Not yet scanned — package must be on npm
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 19d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Your AI writes code without knowing where the landmines are. Omen gives AI assistants the context they need: complexity hotspots, hidden dependencies, defect-prone files, and self-admitted debt. One command surfaces what's invisible. Why "Omen"? An omen is a sign of things to come - good or bad. Your codebase is full of omens: low complexity and clean architecture signal smooth sailing ahead, while high churn, technical debt, and code clones warn of trouble brewing. Omen surfaces these signals…

Keywords
mcp