Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 05:52 UTC

CleanTalk / php-antispam

PHP spam protection. CAPTCHA-free alternative

PHPNo license detected★ 73 stars⑂ 34 forkssince Sep 2013View on GitHub ↗

CleanTalk/php-antispam holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (81/100) and lowest on Security (1/100). It was last updated 4 days ago. 3 contributors account for most of its recent work.

56
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.

56
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 54 is calibrated to 56 on the published index scale (record calibration 2026-08-02).

Ownership

CleanTalkOrganization
25 followers95 public repossince Sep 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistcleantalk/php-antispam4.4.13,8291828 days agoapispamanti-spamantispam

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
8.3/36Commit cadence — 12/52 weeks with commits
12.9/18Commit volume — 26 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year26
human_commit_share1
days_since_last_push4
active_weeks_last_year12
How it's scored
27/27Ships releases — 14 releases published
27/36Release recency — latest release 145 days ago
12.6/27Release cadence — a release every ~300.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tag4.4
releases_from_tagsno
days_since_latest_release145
mean_days_between_releases300.3

Community & Adoption

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

41Weak · 17% of overall
How it's scored
30.1/60Stars — 73 stars
12.7/25Forks — 34 forks
6.5/15Watchers — 16 watchers
Inputs used
forks34
stars73
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, poser.pugx.org
has_pull_request_templateno
How it's scored
47.8/80Monthly downloads — 3,829 downloads/month across packagist
4/20Registry dependents — 3 packages depend on it
Inputs used
packagescleantalk/php-antispam
dependents3
ecosystemspackagist
total_downloads623,515
monthly_downloads3,829
unverified_packages_excluded—

Sustainability & Governance

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

81Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
17.1/22.5Commit distribution — top contributor authored 24% of commits
13.5/13.5Contributor breadth — 20 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor3
contributors_sampled20
top_contributor_share0.24
How it's scored
42/42Issue resolution — 100% of issues closed
23.6/30PR acceptance — 22/28 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs22
open_issues0
closed_issues22
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs6
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
10.2/25Owner reach — 25 followers of CleanTalk
25/25Track record — 95 public repos, account ~13 yr old
Inputs used
followers25
owner_typeOrganization
is_verifiedno
owner_loginCleanTalk
public_repos95
account_age_days4,762

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 28 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescleantalk/php-antispam
ecosystemspackagist
any_deprecatedno
min_days_since_publish28

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://cleantalk.org/antispam
10/10Repository description
10/10Topics — 15 topics
10/10Wiki
Inputs used
topicsphp, antispam, spam, php-api, spam-protection, spam-filter, form-protection, anti-spam, api, rest-api, spam-api, spam-detection, cleantalk, anti-spam-api, spam-detection-api
has_wikiyes
homepagehttps://cleantalk.org/antispam
docs_sitehttps://cleantalk.org/antispam
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestscomposer.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

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.

39Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://cleantalk.org/llms.txt)
6.9/40Legible commit history — 13 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://cleantalk.org/llms.txt
legible_history_share0.13
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/10 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes22,413
source_files_sampled10
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

73GitHub stars
20contributors
26commits, last 12 months
4days since last push
14releases
3bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/CleanTalk/php-antispam: run: RepoClient.LocalPath: error during tarballHandler.setup: internal error: handler.httpClient.Do: Get "https://codeload.github.com/CleanTalk/php-antispam/legacy.tar.gz/refs/heads/master": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: dial tcp 140.82.121.9:443: i/o timeout); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 34 ⇿
0Stars
34Forks
14Releases

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.

01325383312013-112020-032026-08
Major 1Minor 1Patch 2

Each point covers 12 days.

All dependencies 7

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

RegistryPackageVersionRelation
Packagistext-dom—indirect
Packagistphpcompatibility/php-compatibility—indirect
Packagistphpunit/phpunit—indirect
Packagistsquizlabs/php_codesniffer—indirect
Packagistvimeo/psalm—indirect
Packagistwp-cli/wp-cli-bundle—indirect
Packagistyoast/phpunit-polyfills—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — Packagist.