Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 20:32 UTC

crowdsecurity / cs-wordpress-bouncer

CrowdSec is an open-source cyber security tool. This plugin blocks detected attackers or display them a captcha.

PHP · JavaScriptMIT★ 44 stars⑂ 9 forkssince Dec 2020View on GitHub ↗

crowdsecurity/cs-wordpress-bouncer holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (84/100) and lowest on Security (32/100). It was last updated 252 days ago. A single contributor accounts for most of its recent work.

51
overall / 100
Moderate

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

51
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 51 is calibrated to 51 on the published index scale (record calibration 2026-08-02).

Ownership

crowdsecOrganization
616 followers132 public repossince Apr 2020

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

36Weak · 21% of overall
How it's scored
3.6/36Push recencylast push 252 days ago
2.1/36Commit cadence3/52 weeks with commits
7/18Commit volume5 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year5
human_commit_share1
days_since_last_push252
active_weeks_last_year3
How it's scored
27/27Ships releases80 releases published
16.2/36Release recencylatest release 252 days ago
27/27Release cadencea release every ~43.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count80
latest_release_tagv2.13.1
releases_from_tagsno
days_since_latest_release252
mean_days_between_releases43.7

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

45Weak · 17% of overall
How it's scored
26.5/60Stars44 stars
7.5/25Forks9 forks
6/15Watchers13 watchers
Inputs used
forks9
stars44
watchers13
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.5/22.5Commit distributiontop contributor authored 62% of commits
5.4/13.5Contributor breadth4 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.621
How it's scored
37.1/42Issue resolution88% of issues closed
22.3/30PR acceptance99/133 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs99
open_issues5
closed_issues38
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.884
closed_unmerged_prs34
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
20.1/25Owner reach616 followers of crowdsecurity
25/25Track record132 public repos, account ~6 yr old
Inputs used
followers616
owner_typeOrganization
is_verifiedno
owner_logincrowdsecurity
public_repos132
account_age_days2,355

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter config.eslintrc, .php-cs-fixer.dist.php, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests2 out of 10 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://wordpress.org/plugins/crowdsec/
10/10Repository description
10/10Topics20 topics
10/10Wiki
Inputs used
topicscrowdsec-bouncer, wordpress, security, firewall, captcha, ip-scanner, ip-blocker, ip-blocking, ip-address, ip-database, ip-range-check, crowdsec, ban-hosts, ban-management, anti-hacking, hacker-protection, captcha-image, captcha-generator, captcha-generation, captcha-service
has_wikiyes
homepagehttps://wordpress.org/plugins/crowdsec/
docs_sitehttps://wordpress.org/plugins/crowdsec/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

32At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.5/2.5CI-Tests2 out of 10 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities12 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.
How it's scored
15.1/35Direct dependencies free of known advisories1 affected: symfony/cache 5.4.40 (high 7.1)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
34/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 113 days ago
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages32
unassessed_packages18
affected_by_severityhigh 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 32 resolved dependencies against OSV. 18 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

57Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://wordpress.org/llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://wordpress.org/llms.txt
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc, .php-cs-fixer.dist.php, phpstan.neon
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/43 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes41,582
source_files_sampled43
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

44GitHub stars
4contributors
5commits, last 12 months
252days since last push
80releases
1bus factor
5open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch packagist package 'crowdsec/wordpress-bouncer' from its registry

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
65Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0246810922021-022023-112026-08
Major 2Minor 24Patch 39

Each point covers 6 days.

OpenSSF Scorecard 2.4 / 10
2.4aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-18 20:31 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
2CI-Tests2 out of 10 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities12 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Packagistcrowdsec/bouncer^4.3.0composer.json
Packagistsymfony/cache5.4.40composer.json
Packagistsymfony/polyfill-mbstring^1.31.0composer.json
Packagistsymfony/service-contracts^2.5.3composer.json
Packagistcweagans/composer-patches^1.7composer.json
All dependencies 50

Full resolved dependency set from the GitHub dependency graph: 5 direct and 45 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Packagistcrowdsec/bouncer4.3.0direct
Packagistcweagans/composer-patches1.7.3direct
Packagistsymfony/cache5.4.40direct
Packagistsymfony/polyfill-mbstring1.31.0direct
Packagistsymfony/service-contracts2.5.4direct
npm@jest/test-sequencer^29.4.2indirect
npmaxios^0.21.1indirect
npmcross-env^7.0.3indirect
npmeslint^7.32.0indirect
npmeslint-config-airbnb-base^14.2.1indirect
npmeslint-config-prettier^8.3.0indirect
npmeslint-plugin-import^2.24.1indirect
npmeslint-plugin-prettier^3.4.0indirect
npmexpect-playwright^0.8.0indirect
npmhosted-git-info^2.8.9indirect
npmjest^29.4.2indirect
npmjest-circus^29.4.2indirect
npmjest-environment-node^29.4.2indirect
npmjest-playwright-preset^3.0.1indirect
npmjest-runner^29.4.2indirect
npmlodash^4.17.21indirect
npmplaywright-chromium1.52.0indirect
npmprettier^2.3.2indirect
npmws^7.4.6indirect
Packagistcomposer/ca-bundle1.5.6indirect
Packagistcrowdsec/capi-client3.4.0indirect
Packagistcrowdsec/common3.0.0indirect
Packagistcrowdsec/lapi-client3.6.0indirect
Packagistcrowdsec/remediation-engine4.3.0indirect
Packagistgeoip2/geoip22.13.0indirect
Packagistgregwar/captcha1.2.1indirect
Packagistmaxmind-db/reader1.12.0indirect
Packagistmaxmind/web-service-common0.9.0indirect
Packagistmlocati/ip-lib1.20.0indirect
Packagistmonolog/monolog2.10.0indirect
Packagistpsr/cache1.0.1indirect
Packagistpsr/container1.1.1indirect
Packagistpsr/log1.1.4indirect
Packagistsymfony/cache-contracts2.5.4indirect
Packagistsymfony/config5.4.46indirect
Packagistsymfony/deprecation-contracts2.5.4indirect
Packagistsymfony/filesystem5.4.45indirect
Packagistsymfony/finder5.4.45indirect
Packagistsymfony/polyfill-ctype1.31.0indirect
Packagistsymfony/polyfill-php731.31.0indirect
Packagistsymfony/polyfill-php801.31.0indirect
Packagistsymfony/polyfill-php811.31.0indirect
Packagistsymfony/polyfill-uuid1.31.0indirect
Packagistsymfony/uid5.4.45indirect
Packagistsymfony/var-exporter5.4.45indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 32 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 1 are direct. 18 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
symfony/cache5.4.40directhigh18.0.12

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.