WordPress

WordPress/WordPress

WordPress, Git-ified. This repository is just a mirror of the WordPress subversion repository. Please do not send pull requests. Submit pull requests to https://github.com/WordPress/wordpress-develop and patches to https://core.trac.wordpress.org/ instead.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 16, 2026
today
Ship score
84/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 21,375 → 21,473 (Sep 1 – Oct 13, 2026)
+55 stars in the 28 days to 2026-10-13

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
21.5K
Forks
13K
Open issues
3
Watchers
1.4K
Primary language
PHP
License
Other
Created
Dec 1, 2011
Owner
WordPress · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 27 startups in the directory ship primarily in PHP.

Topics

This repository has no GitHub topics.

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 16% (self-hostable 79%, hosted offering 68%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-16This is the badge for WordPress/WordPress, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/WordPress/WordPress.svg)](https://ossean.com/WordPress/WordPress)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.