7/10

Contribution Checker

contribute.postiz.com

Does Contribution Checker have a moat?

No.

17/100 · Moatless

“The gate is a weekend build, and GitHub can ship the same thing natively. Only Postiz's name and Nevo David's 26k X followers help it spread.”

Code to copy

a week

Moat to cross

2 weeks

Market

A few rivals

Share on X
Moat depth
MoatlessShallowReal

Revenue not verified. Founders can list on TrustMRR to show it here.

01/The verdict

A self-hosted, AGPL-3.0 GitHub App that closes pull requests from authors who haven't applied or been approved, reopens them on approval, and also adds CLA/DCO checks and a 36-heuristic quality score. Maintainers of open-source repos are the users.

The product is a webhook handler, a Postgres table and a form. It is open source under AGPL-3.0, so a rival can fork it. The only real edge is the Postiz brand and founder Nevo David (about 26k X followers, known for open-source growth). That could bring early adopters, but it is not a moat. GitHub could also add this as a built-in setting.

02/1 moat

Time won't do it

Nevo David has about 25.9k X followers and a name in open-source growth through Postiz and his Gitroom consultancy. Postiz's main repo already runs the checker on its own pull requests, which shows it works and gives it visibility.

To cross it: A challenger needs a maintainer with a comparable audience to endorse and use their tool, which money doesn't buy.

03/The gap

Easy to copy

  • A GitHub App that closes pull requests and reposts a comment is a few webhook handlers, and the code is public under AGPL-3.0 for anyone to fork.
  • The 36 non-AI heuristics (diff size, profile age, PR body) are ordinary functions a rival can rewrite or improve in days.
  • CLA and DCO checks are already sold by established apps and are easy to copy.
  • The application form and approval list have no data lock-in. Moving to another tool means exporting a list of logins.

How you'd go after it

  • Offer a hosted, zero-setup version, since this one needs self-hosting on your own Postgres.
  • Build on a shared reputation signal, such as a cross-repo trusted-contributor list, so maintainers don't vet every author themselves.
  • Ship it free inside a bigger maintainer toolkit, such as triage, labels and spam detection.
  • Wait for GitHub to add native contributor gating, which would make a third-party app unnecessary.

04/Build against it?

Only with an edge

Only worth building with an edge, such as a hosted product or a shared cross-repo reputation list. A plain gating bot is a weekend project, free and open source, and GitHub could build it natively.

Already selling this:VouchPR Slop StopperCLA AssistantDCO GitHub AppGitHub native PR/contributor restrictionsProbot-based moderation bots

Does yours?

Paste your website. You get your score in about a minute.