WI

Wikimedia Gerrit

Wikimedia Gerrit is the code review system of the Wikimedia movement where developers maintain public accounts and contribute changes to MediaWiki and related projects.

122 usesUpdated Oct 10, 2026
Pseudonym
gerritwikimediacode reviewmediawikideveloperusername

About this module

Wikimedia Gerrit hosts the public code review workflow behind MediaWiki, Wikimedia extensions and the infrastructure that runs Wikipedia and its sister projects. Every contributor has a public account identified by a username, a display name and a current status note. This module resolves a username to that public account, including when it was registered and when the contributor last touched a change.

Related modules

NUPseudonym
NuGet
NuGet is the package manager and central package gallery for the .NET ecosystem.
THPseudonym
The BigBoss
Find a public The BigBoss author page by username.
JUPseudonym
Jupyter Forum
Find an exact Jupyter Forum member and return public identity, profile, role, date, badge, and activity details.
GIPseudonym
GitBook
Resolve a GitBook subdomain username and return its public documentation-site metadata.
BOPseudonym
Boot.dev
Check whether an exact public learning-profile handle is registered on Boot.dev.
ANPseudonym
Anaconda.org
Anaconda.org is a package hosting and collaboration platform for conda software, channels, organizations, and public user profiles.
STPseudonym
StackBlitz
Find a public developer profile on the StackBlitz online development platform.
SUPseudonym
Sublime Text Forum
Sublime Text Forum is a public discussion community for Sublime Text users, package authors, and developers.

Rate limits

Pick the right plan for higher usage limits.

TierPer hourPer dayCooldownAction
Guest2 req/h3 req/day10sCurrent plan
Free10 req/h20 req/day5sSign up
Standard60 req/h200 req/day2sSee pricing
Pro100 req/h500 req/day2sSee pricing
Ultimate500 req/h2000 req/day0sSee pricing

Frequently Asked Questions

What impacts module results and how to interpret changes across executions.

Results depend on source platform availability, anti-automation controls, and temporary service limits. A valid target can still return partial or empty data when the upstream platform is rate-limited or unavailable.