Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-19 02:38 UTC

openswoole / swoole-src

Programmatic server for PHP with async IO, coroutines and fibers

C++ · PHPApache-2.0★ 858 stars⑂ 55 forkssince Oct 2021View on GitHub ↗

openswoole/swoole-src holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (74/100) and lowest on Security (33/100). It was last updated 123 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

OpenswooleOrganization
461 followers15 public repossince Aug 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistopenswoole/ext-openswoolepoints to another repo — not scoreddev-master8-123 days agoextensionopenswooleext-openswooleopen-swoole

Metrics by category

Vitality

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

48Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 123 days ago
3.5/36Commit cadence5/52 weeks with commits
16.3/18Commit volume65 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_year65
human_commit_share
days_since_last_push123
active_weeks_last_year5
How it's scored
27/27Ships releases16 releases published
27/36Release recencylatest release 140 days ago
12.6/27Release cadencea release every ~166.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count16
latest_release_tagv26.2.0
releases_from_tagsno
days_since_latest_release140
mean_days_between_releases166.2
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

64Moderate · 17% of overall
How it's scored
47.6/60Stars858 stars
14.4/25Forks55 forks
6.7/15Watchers17 watchers
Inputs used
forks55
stars858
watchers17
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateyes
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.2/22.5Commit distributiontop contributor authored 55% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 54 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.547
How it's scored
30.6/42Issue resolution73% of issues closed
27.8/30PR acceptance186/201 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/5 approved changesets -- score normalized to 0
Inputs used
merged_prs186
open_issues49
closed_issues131
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.728
closed_unmerged_prs15
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
19.2/25Owner reach461 followers of openswoole
18.5/25Track record15 public repos, account ~4 yr old
Inputs used
followers461
owner_typeOrganization
is_verified
owner_loginopenswoole
public_repos15
account_age_days1,786
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://openswoole.com
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsopenswoole, php, async, coroutines, concurrency
has_wikiyes
homepagehttps://openswoole.com
docs_sitehttps://openswoole.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

33At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/5 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 54 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate 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-Releasesno data
0/7.5Token-Permissionsno data
2.2/7.5Vulnerabilities7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. 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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC++ (statically typed)
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC++ (statically typed)
53.1/55Manageable file sizes14/404 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes192,587
source_files_sampled404
oversized_source_files14
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 examplessamples
Inputs used
example_dirssamples
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

858GitHub stars
100contributors
65commits, last 12 months
123days since last push
16releases
1bus factor
49open issues
Packagistpackage ecosystems

Data collection warnings

  • packagist package 'openswoole/ext-openswoole' points at a different repository (https://github.com/openswoole/ext-openswoole); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 3.3 / 10
3.3aggregate

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-07-19 02:38 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/5 approved changesets -- score normalized to 0
10Contributorsproject has 54 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate 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
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
3Vulnerabilities7 existing vulnerabilities detected
All dependencies 25

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

RegistryPackageVersionRelation
Packagistclue/stream-filter1.7.0indirect
Packagistguzzlehttp/guzzle7.9.2indirect
Packagistguzzlehttp/promises2.3.0indirect
Packagistguzzlehttp/psr72.8.0indirect
Packagistnyholm/psr71.8.2indirect
Packagistphpindirect
Packagistphp-http/client-common2.7.3indirect
Packagistphp-http/discovery1.20.0indirect
Packagistphp-http/httplug2.4.1indirect
Packagistphp-http/message1.16.2indirect
Packagistphp-http/message-factory1.1.0indirect
Packagistphp-http/promise1.3.1indirect
Packagistpsr/container2.0.2indirect
Packagistpsr/http-client1.0.3indirect
Packagistpsr/http-factory1.1.0indirect
Packagistpsr/http-message2.0indirect
Packagistpsr/log3.0.2indirect
Packagistralouphie/getallheaders3.0.3indirect
Packagistsymfony/deprecation-contracts3.6.0indirect
Packagistsymfony/http-client7.4.6indirect
Packagistsymfony/http-client-contracts3.6.0indirect
Packagistsymfony/options-resolver8.0.0indirect
Packagistsymfony/polyfill-php801.33.0indirect
Packagistsymfony/polyfill-php831.33.0indirect
Packagistsymfony/service-contracts3.6.1indirect
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.14.0 — full methodology · metrics wiki.

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