The WPFolks app is out on iPhone and Android. Free, no ads. Download on the App Store Get it on Google Play
Skip to main content
Login Join
Transparency

How the leaderboard works.

Every point in your score has a reason. Here's exactly where they come from, what's capped, and what isn't.

Two ranks: Community Impact and Total.

The leaderboard ranks folks two ways. The default is Community Impact. You can switch to the Total ranking using the "All Time (Total)" tab.

Community Impact is the rank for folks who do real WordPress contribution AND engage with this community. It weights wp.org work (team memberships, adoption of your plugins and themes, recognized contributor badges) alongside on-site quality signals (Verified and Expert badges, other WPFolks badges, shipped outcomes, distinct folks who upvoted your work). Bulk-importing snippets or videos to farm score does not move this number. Real wp.org work always counts something (a 30 percent baseline), and unlocks fully as you participate here.

Total is the on-site activity rank. Every scoring event you trigger here adds to it: submissions, feed posts, attended events, reviews, certifications, every shipped outcome. It's the right rank for tracking your day-to-day participation. Wp.org credit is capped on Total so a wp.org legend can't dominate from outside contribution alone.

Hover the score on the leaderboard to see both numbers side by side.

How the Community Impact rank is built.

Community Impact rewards folks who do real WordPress work AND show up here. It weights wp.org work (team membership, adoption of your plugins and themes, recognized contributor badges) alongside on-site quality signals (identity badges, shipped ideas and roadmap items, distinct folks who upvoted your work). It does not reward posting volume. A plugin author with 100K real-user installs ranks above a folk who bulk-imported 50 snippets nobody upvoted.

Wp.org credit scales with on-site activity. Real WordPress work always counts something here (a baseline 30 percent of your wp.org credit is granted regardless), and the rest unlocks as you participate. Verifying your profile gets you off the floor; combining that with WPFolks badges, shipped ideas or roadmap items, and earning upvotes from other folks unlocks full credit. The intent is simple: this is the rank for folks who contribute to WordPress AND engage with this community. A wp.org legend who never participates here can still appear on the board, just not above active community members.

Values below are live from the codebase.

WP.org team membership (combined cap 250)

Core, Core Performance, or Core AI team
+75
Plugin Reviewer or Theme Reviewer
+60
Accessibility or Meta team
+50
Standard contributor team
Polyglots, Documentation, Support, Community, Marketing, Training, WordPress TV, Design, Mobile, Meetup, WordCamp, CLI, Media Corps.
+30
Combined team-membership ceiling
Across all teams. Three strong team affiliations (Core + Plugin Reviewer + Theme Reviewer = 195) is roughly equivalent to being on every team. Beyond this, team-count stops compounding so on-site contribution becomes the differentiator.
250 max
Recognised Core Contributor (separate signal, outside the cap)
+75

WP.org adoption (sqrt-scaled, cap 800)

Authored plugin or theme with 1K+ installs
Sqrt scaling: 1 item = +20, 4 items = +40, 16 items = +80, 100 items = +200. Quality compounds slower than quantity.
+20 per item (sqrt)
10K+ installs
+50 per item (sqrt)
100K+ installs
+100 per item (sqrt)
1M+ installs
Total across all four tiers is capped at 800. If sqrt-scaled sum exceeds 800 it is scaled down proportionally so the relative tier weighting is preserved.
+200 per item (sqrt)
Author only
Adoption signal is awarded only when the folk is the author of the plugin or theme. Contributing to someone else's work does not award adoption points here (it still counts toward the Total rank).
Contributors: 0

WPFolks badges

Verified badge
+50
Expert badge
+50
Each other WPFolks badge held
Includes referral tiers, follower tiers, reaction tiers, course completers, and the rest of the registry. Plugin and theme contributor tier badges are excluded here because the wp.org work they represent is already credited via the adoption signal above. Caps at 25 badges so a long badge list does not overpower other Community Impact signals. See the full list at /badges/.
+3 each, cap 75

Folks Academy

Each completed session you hosted
Caps at 10 hosted sessions. Primary hosts and co-hosts both earn this signal.
+20 each, cap 200
Speaker badge (1 session hosted)
Awarded as a profile badge to mark your first session, but does not add Impact points. The +20 per-session signal above already credits the milestone.
0
Mentor badge (5 sessions hosted)
Replaces lower tiers in the Impact breakdown. Only the highest tier you hold is counted.
+50
Master badge (15 sessions hosted)
+100
Legend badge (50 sessions hosted)
Top of the speaker ladder.
+200
Each session you attended (learner)
Earned by entering the attendance code the host shared during the session. One learner badge per contribution track.
+5 each (uncapped)

WordCamp & community speaking

WordCamp / meetup talk delivered
Maxes at 5 talks.
+15 each, cap 75

Shipped outcomes (capped)

Idea you posted got shipped
Maxes at 5 shipped ideas. Beyond that, additional shipped ideas still award Total-rank points; they just stop adding to Community Impact.
+50 each, cap 250
Roadmap item you submitted got shipped
Maxes at 10 shipped roadmap items.
+25 each, cap 250

Engagement from other folks (capped)

Distinct folks who upvoted your work
Maxes at 1,000 distinct voters. The cap stops this from becoming a proxy for "how many items did you publish"; reach matters, but a folk with one upvoted flagship still ranks above someone with 200 thinly-upvoted items.
1 pt per 5 distinct voters, cap 200

Penalties (mild)

Bulk submission cluster (5+ same-type posts within 1 hour)
Detected per 30-day window. Mild discouragement for batch-import farming.
-10 each

Theoretical maximum from Community Impact: roughly 2,200 points if a folk hits every visible ceiling at once (Core team, Core Contributor flag, full adoption cap, both identity badges, Academy Legend + 10 hosted sessions, 5 WordCamp talks, both shipped caps, full upvoter cap). In practice, the leaderboard is competitive across the 300 to 1,200 range.

How the Total rank is built.

The Total rank is the running sum of every scoring event ever credited to a folk. Two rules shape it: on-site activity is largely uncapped (every submission, every feed post, every certification, every event check-in counts), and external (wp.org) signals are bounded so a folk can't dominate from outside contribution alone.

Some signals appear in both the Community Impact and Total tables (wp.org plugins, badges, shipped outcomes). That's intentional. Each rank scores those actions with its own weights and caps, so you'll see the same plugin earn different point values under each rank.

Live values straight from the codebase. If a number changes, this page changes with it.

Identity

Profile completion
0.3 pt per %, max 30
Connect wp.org profile
+20 (one-time)
Core Contributor (wp.org)
+50 (one-time)

WP.org footprint (capped)

Published wp.org plugin or theme
Plugins and themes share one bucket. 5 items combined maxes it. Plugins/themes where you are a contributor (not author) count at 10% of the authored weight.
+10 each, cap 50
Active installs (plugins)
50,000 installs maxes the bucket. Installs on plugins where you are a contributor (not author) count at 10% of the authored weight. So a contributor on a 1M-install plugin counts as 100K toward this bucket, not 1M.
+1 per 1,000, cap 50
Theme downloads
50,000 downloads maxes the bucket. Same contributor-vs-author rule as plugin installs above.
+1 per 1,000, cap 50
WP.org contribution badge
5 badges maxes the bucket.
+8 each, cap 40

Certifications

WP VIP Advanced Professional
Uncapped. The WordPress-native apex credential.
+150 (one-time)
WP VIP individual course
Awarded per VIP course completed (Platform Standards, Performance, CLI, etc.). Lifetime cap of 200 pts across all VIP courses.
+40 each (cap 200)
Marketplace cert (Codeable, Toptal, etc)
Counts toward the 100-pt non-VIP cert ceiling (Marketplace + Niche + Other combined).
+100 each
Niche cert (AWS, Google, Azure, etc)
Counts toward the 100-pt non-VIP cert ceiling.
+80 each
Other professional cert (LinkedIn, Udemy, etc)
Counts toward the 100-pt non-VIP cert ceiling.
+40 each

On-site submissions (uncapped)

Plugin (native, no wp.org slug)
+3
Theme (native, no wp.org slug)
+3
Business
+3
Roadmap item (bug or feature)
+3
Folks TV course
+3
Resource
+1
Snippet
+1
Idea
+1
Deal
+1
Event
+1
Talk
+1
Job posting
+1
Folks TV video
+1

Submission outcomes (uncapped)

Idea you posted gets shipped
Awarded to the original poster.
+15
You shipped someone else's idea
Awarded to every claimer credited with shipping (1.23.71: reduced from 50 per claimer so multi-claim teams don't inflate scores).
+20
Your roadmap item marked Shipped
Awarded to the submitter.
+5
Comment posted on a roadmap item
+1
A roadmap item you commented on shipped
Awarded once per item per commenter.
+1

Folks TV: creating and recognition

Upvote received on a video you submitted
+1 each, capped at 50 total
Your video crosses 10 upvotes
+5 (one-time per video)
Your video crosses 50 upvotes
+10 (one-time per video)
Your video crosses 100 upvotes
+15 (one-time per video)
Your video crosses 100 watched-views
+5 (one-time per video)
Your video crosses 1,000 watched-views
+10 (one-time per video)
Cumulative views across all your videos: 100
+5 (one-time)
Cumulative views: 1,000
+20 (one-time)
Cumulative views: 10,000
+50 (one-time)
Your video selected as Weekly Pick
+20 (one-time per video)
First folk completes a course you created
+50 (one-time per course)
Credited as presenter on a video
+2

Folks TV: participation (uncapped)

Asset pinned to a video timestamp
+1
"What to watch next" suggestion
+1
Suggestion validated (5 upvotes)
+3
Outdated flag confirmed
+2
Video completed (≥90% watched)
+1
Course module completed
+15
Cumulative watch time: 5 hours
+5 (one-time)
Cumulative watch time: 25 hours
+20 (one-time)
Cumulative watch time: 100 hours
+50 (one-time)

Referrals (capped on points, uncapped on tier badges)

Verified-signup invite via your link
The point reward maxes out at 50 verified invites. Tier badges (Connector, Hall of Fame, Legendary Folk, Pioneer, etc.) keep firing past that, so the recognition continues even after the points stop.
+5 each, cap 250
Self-referrals and unverified accounts
Excluded

Community activity (mostly uncapped)

Top-level feed post
+2
Feed reply
+1
Upvote received on your work
+2
Reactions received on your feed post
+1 per 2 reactions
Event attended
Total maxes out at 6 events. Encourages real attendance over score-farming.
+5 each, cap 30
Review posted
+1

Internal badges (one-time)

Each WPFolks-internal badge held
Includes Verified, Expert, Trailblazer, Connector, Hall of Fame, Pioneer, and the rest. See the full list at /badges/. Total from badges is naturally bounded by the registry size.
+5

How your score updates.

  • Most events update your score the moment they happen. A submission lands, a vote comes in, an event check-in hits the table, you see the update.
  • A reconciler runs every 5 minutes and again every hour as a safety net. If a hook ever misfires, the next pass picks it up.
  • Items submitted as Pending only score when an admin approves them. The submission alone does not credit points.
  • Day-to-day, Total scores only move up. Live data drift (a plugin install count dropping, a profile field clearing) does not remove credit. Two exceptions: an admin revert (logged in the audit trail), and a scoring-algorithm update. When the points-per-action values change, past events get retroactively repriced so every folk is scored under the same rules. Community Impact, by contrast, is computed live from current state every hour, so it can move down too (for example, the activity multiplier rebalances if your on-site engagement changes, or a cap is added).

How the two ranks are stored.

Total is ledger-based. Every point added to your Total writes one row to an append-only ledger. Your Total is the sum of those rows. Rows are never deleted, only compensated by reverts (which write a negative row pointing back at the original). Nothing happens silently, and the audit trail stays intact when an admin needs to correct an error.

Community Impact is state-based. Community Impact is computed live from your current state (badges held, plugins/themes published, distinct upvoters, shipped outcomes, etc.) every hour. It does not write to the ledger. When the formula updates, every folk is rescored under the same rules on the next pass. There is no per-event row to revert; if something looks wrong, the fix is in the formula or in the underlying data.

Who can change your score.

  • The system, automatically, when you do something that the registry knows about. This is the bulk of every score on the board.
  • An admin, manually, in two cases: a one-off grant (recognising work the system cannot detect, like reporting a security issue) or a revert (correcting a wrongly-fired event).
  • Nothing else. You cannot self-credit, and there is no payment path to points.

Common questions.

What's the difference between Community Impact and Total? +

Two different questions, two different ranks. Community Impact asks: how much real WordPress contribution does this folk have, both on wp.org and on this site? It weights quality signals and discounts wp.org credit if you don't participate here at all. Total asks: how much activity does this folk have on the site overall? Every action you take here counts (uncapped), with wp.org credit bounded at the top. Use Community Impact to find folks doing the deepest WordPress work; use Total to track your day-to-day momentum on this site.

Why is my Community Impact lower than I expect, even though I have a strong wp.org footprint? +

Community Impact applies an activity multiplier to your wp.org credit. With zero on-site activity, your wp.org sub-score is granted at 30 percent. The multiplier scales up from there based on how much you contribute on this site (identity badges, shipped ideas and roadmap items, WordCamp talks, distinct folks who upvoted your work). Verifying your profile is a good first step but is not enough on its own to unlock full credit. The intent is to reward folks who do real WordPress work and also genuinely engage with the community here.

I submitted a plugin / job / event two days ago and don't see points yet. +

Submissions go in as Pending until an admin approves them. The points fire on approval, not on submit. If approval is taking too long, ping support.

Can my score ever go down? +

For Total: yes, in two cases. An admin revert (correcting a wrongly fired event, logged in the audit trail), or a scoring-algorithm update where points-per-action values are tuned and past events are retroactively repriced. Live data drift like a plugin install count dropping does not remove Total credit. For Community Impact: it can also shift down when the formula updates or when caps are added, since Community Impact is computed live from current state every hour instead of accumulated from a ledger.

Are there bonus points for streaks or daily activity? +

Not today. The current model rewards specific actions and outcomes, not session frequency. If a streak signal would be useful, it can be added without resetting anyone's score.

Will the formula change? +

Yes, when the data tells us to. Points get tuned when a bucket starts dominating the board, losing meaning, or being gamed. Updates apply to past scores too. For Total: if a per-action value drops, past events get repriced; if a cap is added, excess events get trimmed. For Community Impact: the next hourly recompute uses the new formula for everyone at once. This keeps the leaderboard fair for folks who joined after a rule changed.

Where can I see the events that built my score? +

Admins can see the Total ledger and the Community Impact breakdown. A self-serve view is on the roadmap. If you want to see the math behind your number today, message support and we'll walk through it.

See the leaderboard →

Proudly supported by