Software Alternatives & Startups
Register | Login

CodeRifts VS ShellNewHandler

Compare CodeRifts VS ShellNewHandler and see what are their differences

CodeRifts

Contract-change decisions with signed, offline-verifiable receipts: a change to an API or MCP contract merges only with a grant bound to that exact change.

Rating
0 reviews
Pricing
Freemium $149 / Monthly (Team, after the public beta)
Promote on VibeVoted
Alternatives Is it good?
ShellNewHandler

SourceForge.net: ShellNewHandler details page

Rating
0 reviews
Promote on VibeVoted
Alternatives Is it good?
DisplaySwitcher
Switch your monitor’s video input and seamlessly transfer text and files! A Linux/macOS/Windows Desktop Application. sponsored
Note: These products don't have any matching categories. If you think this is a mistake, please edit the details of one of the products and suggest appropriate categories.

Which is more popular?

Based on our record, ShellNewHandler seems to be more popular. It has been mentioned 2 times since March 2021.

social mentions
0 vs 2
DevOps Tools popularity
100% vs 0%

Base details

Website, pricing, platforms and company facts side by side.

CodeRifts
ShellNewHandler
Website coderifts.com sourceforge.net
Pricing
Freemium $149 / Monthly (Team, after the public beta) Official pricing
—
Platforms
Web CLI REST API MCP +1
—
Company 2026 —
Listed in
Developer Tools DevOps Tools API Tools Git Tools AI Developer Tools +2
Cloud Storage Monitoring Tools File Sharing Website Monitoring +1

About CodeRifts and ShellNewHandler

In their own words, as submitted to SaaSHub.

CodeRifts
ShellNewHandler

CodeRifts decides whether a change to an API or MCP contract may merge, and signs the decision. A GitHub App and a GitHub Action post two checks on every pull request that touches a contract file: CodeRifts / issuer and CodeRifts / contract-gate. Require both in branch protection, and a breaking...

Read more about CodeRifts

No description of ShellNewHandler yet.

Features and specs

What each product offers, as listed by its team.

CodeRifts 11 features
ShellNewHandler 0 features
  • Signed decision receipts
    Every decision comes with a signed receipt you can verify offline, without asking CodeRifts.
  • Policy Engine
    Breaking budgets, freeze windows, approval matrix
  • Breaking Change Detection
    10+ change types, OpenAPI schemas
  • Offline Verification (OVSE)
    A public, MIT-licensed verifier checks any receipt with no API key, no account and no CodeRifts server in the loop.
  • MCP server with three tools
    preflight_change_set, verify_receipt and get_decision_details, listed in the official MCP Registry; works with Claude Code, Cursor and custom hosts.
  • Merge enforcement on GitHub
    A required, app-bound status check stays red until a grant exists; enforce_admins on, workflow pinned by SHA.
  • Published proof boundaries
    The 'does not prove' limits are served live at /.well-known/coderifts.json — what a decision does not establish is a field in the output, not a footnote.
  • Named-state verdicts
    CONTINUE, CONTINUE_WITH_MONITORING, REQUEST_APPROVAL or STOP — a state you can branch on, never a score or a boolean.
  • Single-use grants
    One grant, one execution; an adapter that cannot prove atomic consumption cannot report the atomic success state.
  • Guarded tool table for AI agents
    In the tool table handed to the agent, an ungranted mutation does not exist — nothing to call, not an error.
  • Multi-protocol contract diff
    Breaking-change detection for OpenAPI, GraphQL, gRPC, AsyncAPI and MCP tool schemas, with the same signed verdict on every path.

No features have been listed yet.

Analysis

An editorial look at what each product does well and who it suits.

CodeRifts
ShellNewHandler

Overall verdict

  • I don't have verified, up-to-date information about CodeRifts (coderifts.com) to make a confident assessment of its quality, legitimacy, or value. I'd recommend researching independently before making any decisions about this service.

Why this product is good

  • Insufficient reliable data available to confirm the platform's features, pricing, or track record
  • No verified user reviews or reputation signals could be assessed to gauge customer satisfaction
  • Unable to confirm the legitimacy, security practices, or business longevity of this specific service

Recommended for

  • Individuals willing to conduct their own due diligence, including checking domain age, reviews on independent platforms, and any regulatory or security red flags
  • Users who can verify the service directly through trusted sources like the Better Business Bureau, Trustpilot, or relevant industry forums before committing

Overall verdict

  • ShellNewHandler is a niche, lightweight utility hosted on SourceForge designed to give users more control over the Windows 'New' context menu (the ShellNew menu). It can be considered good for its specific narrow use case, but it is an older, minimally maintained tool that may not suit all users, especially those on modern Windows versions.

Why this product is good

  • Provides direct control over customizing the Windows right-click 'New' menu, allowing users to add or remove file type entries
  • Lightweight and free, without bundled bloatware typical of some other free utilities
  • Simple and focused in scope, making it easy to understand for its specific purpose
  • Open distribution via SourceForge allows transparency and no-cost access

Recommended for

  • Power users who want to declutter or customize the Windows New context menu
  • IT administrators managing standardized desktop environments across multiple machines
  • Users comfortable with older utility-style tools and Windows registry-related tweaks
  • Not recommended for casual users seeking modern, actively supported software with regular updates

Category popularity

How often each product is chosen within a category, 0–100% relative to the other.

Score bands 0–20 21–40 41–50 51–60 61–100
CodeRifts
ShellNewHandler
100% 100%
DevOps Tools
0% 0%
0% 0%
File Sharing
100% 100%
100% 100%
Git Tools
0% 0%
0% 0%
Cloud Storage
100% 100%

Questions & Answers

As answered by people managing CodeRifts and ShellNewHandler.

What's the story behind your product?

CodeRifts's answer

A field rename broke a POS system across 19 restaurants for a week. The PR passed review, tests were green, nobody checked the contract. CodeRifts started as the check that catches this before merge. Then the author of the change stopped being a person: AI agents now propose and execute contract changes, and the question became not just "is this safe" but "was this authorized, and can you prove it later" — which is what the signed, offline-verifiable gate answers.

Which are the primary technologies used for building your product?

CodeRifts's answer

Node.js and Express; Ed25519 signatures with a pinned public keyring; PostgreSQL on Railway; an MCP server with three tools listed in the official MCP Registry; the GitHub Apps and Checks API for merge enforcement; a JavaScript and Python receipt verifier (MIT); Cloudflare Pages for the site. Verified live with npx @coderifts/conformance.

What makes your product unique?

CodeRifts's answer

Every decision CodeRifts makes is an Ed25519-signed receipt that anyone can verify offline — no API key, no account, no CodeRifts server in the loop. The verdict is a named state (CONTINUE, CONTINUE_WITH_MONITORING, REQUEST_APPROVAL, STOP), not a score, and it ships with its own published limits: the "does not prove" statements served live at /.well-known/coderifts.json. Where authorization cannot be established, the answer is never an assumed yes.

Why should a person choose your product over its competitors?

CodeRifts's answer

Diff tools tell you what changed in a contract. CodeRifts decides whether an AI agent may proceed with that change, spends a single-use grant on execution, and keeps the GitHub required check red until the grant exists — and the evidence survives us: the receipt verifies against a pinned key snapshot with a public MIT verifier. If your question is "who allowed that, and can I prove it without trusting the vendor's database", that is the difference.

How would you describe the primary audience of your product?

CodeRifts's answer

Three people. The one who runs AI agents in production and needs "who allowed that change" to be more than a log line they also control. The one adding a gate to an agent runtime who needs a state to branch on, not a score. And the one an auditor will ask, who needs evidence that survives the vendor. If none of these is you yet, you probably do not need this today.

Who are some of the biggest customers of your product?

CodeRifts's answer

  • No paying customers yet. CodeRifts is in beta; the first external organization onboarding is the milestone we publish next — not before.

User comments

Share your experience with using CodeRifts and ShellNewHandler. For example, how are they different and which one is better?

Log in or Post with

Social recommendations and mentions

Recommendations tracked on public social media and blogs since March 2021.

CodeRifts 0 mentions
ShellNewHandler 2 mentions

Tracking CodeRifts since Mar 2026.

  • I recently got libreoffice, but now the new option in right click looks like a mess. Can someone help me get rid of them please?
    Use Shell New Handler. Run the portable app and simply untick the items you don't want to appear in your new context menu. Source: about 4 years ago
  • This menu should be easy to add/remove programs to... Who is really creating Access Databases from this menu often enough to keep it here? (Not me!) Is there an easy way to edit this?
    I've always used ShellNewHandler for this. It's a really simple portable utility that allows you to remove most of the items from that menu. Tested it out on Windows 11 and it's still compatible. Source: over 5 years ago

Alternatives to CodeRifts and ShellNewHandler

When comparing CodeRifts and ShellNewHandler, you can also consider the following products.

Loading...