io.github.Rosentic/rosentic

MCPcommunity
v0.1.1io.github.RosenticUnknownUpdated 1mo agoGitHub

Deterministic cross-branch conflict detection for AI coding agents

Rosentic checks whether your active branches are compatible with each other before merge. It detects broken function signatures, HTTP route conflicts, and schema mismatches across 15+ languages using deterministic AST analysis. This is not AI code review. Rosentic finds structural contract conflicts that would cause runtime failures after merge - the kind of breaks that tests don't catch because…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.Rosentic
LicenseUnknown
Version0.1.1
Sourcemcp-registry
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 · clean+30/30
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✓ Cleanv0.1.1 · 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

Rosentic checks whether your active branches are compatible with each other before merge. It detects broken function signatures, HTTP route conflicts, and schema mismatches across 15+ languages using deterministic AST analysis. This is not AI code review. Rosentic finds structural contract conflicts that would cause runtime failures after merge - the kind of breaks that tests don't catch because they only run on one branch at a time. Then add to your editor's MCP config: Works with Cursor,…

Keywords
mcp