WPScan - WordPress Security

WPScan - WordPress Security

@wpscanteamOpen source projects from wpscanteam

Updated: 2025-06-13(303d ago)GitHub API fallback9 repositories

Portfolio Shape

100%

of the visible star count comes from this organization's top three repositories.

Average Repository Size

1.1K

stars per repository in this same snapshot.

Current Mix

Ruby

is the most common language here, with 2 repositories updated in the last 90 days.

Why this rank

This organization stands out because one flagship repo drives 98% of its visible star count.

Flagship share 98%Breakout repo: wpscan

Organization pages work best when you separate portfolio breadth from flagship concentration. In WPScan - WordPress Security's case, the visible top three repositories account for about 100% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.

The dominant language mix here is Ruby (5), PHP (2), Python (1). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.

Source: GitHub API fallback. This is the same cache-first snapshot used by the organization ranking list, so the summary view and the detail view should stay aligned.

Top Repositories

#RepositoryLanguage⭐ Stars
1wpscanteam/wpscan

WPScan WordPress security scanner. Written for security professionals and blog maintainers to test the security of their WordPress websites. Contact us via contact@wpscan.com

Ruby9.5K
2wpscanteam/CMSScanner

CMS Scanner Framework

Ruby131
3wpscanteam/VulnerableWordpressPHP44
4wpscanteam/wpspider

Wordpress.org svn repositories spider

Python12
5wpscanteam/homebrew-tap

WPScan's OFFICAL Homebrew Tap

Ruby8
6wpscanteam/WordpressLab

WordpressLab - Experimental

PHP6
7wpscanteam/ToolsRuby4
8wpscanteam/blog

WPScan Blog

HTML3
9wpscanteam/OptParseValidator

optparse standard lib extended & validators

Ruby3

How to Read This Snapshot

Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.

For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.