Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 21:21 UTC

thephpleague / openapi-psr7-validator

It validates PSR-7 messages (HTTP request/response) against OpenAPI specifications

PHPMIT★ 562 stars⑂ 109 forkssince Sep 2019View on GitHub ↗

thephpleague/openapi-psr7-validator holds a health index of 30 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (72/100) and lowest on Security (26/100). It was last updated 76 days ago. A single contributor accounts for most of its recent work.

30
overall / 100
At Risk

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.

30
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 56 is calibrated to 59 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

946 followers159 public repossince Dec 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistleague/openapi-psr7-validator0.24500,0003897 days agohttpvalidationopenapipsr7

Metrics by category

Vitality

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

51Moderate · 21% of overall
How it's scored
18/36Push recencylast push 76 days ago
3.5/36Commit cadence5/52 weeks with commits
10/18Commit volume12 commits in the last year
4/10OpenSSF Scorecard: Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year12
human_commit_share0.99
days_since_last_push76
active_weeks_last_year5
How it's scored
27/27Ships releases37 releases published
27/36Release recencylatest release 97 days ago
12.6/27Release cadencea release every ~187 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count37
latest_release_tag0.24
releases_from_tagsno
days_since_latest_release97
mean_days_between_releases187
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?

67Good · 17% of overall
How it's scored
44.6/60Stars562 stars
16.9/25Forks109 forks
7.1/15Watchers20 watchers
Inputs used
forks109
stars562
watchers20
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_servicesposer.pugx.org, shields.io
has_pull_request_templateno
How it's scored
76/80Monthly downloads500,000 downloads/month across packagist
12.6/20Registry dependents77 packages depend on it
Inputs used
packagesleague/openapi-psr7-validator
dependents77
ecosystemspackagist
total_downloads18,100,914
monthly_downloads500,000
unverified_packages_excluded

Sustainability & Governance

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

72Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.7/22.5Commit distributiontop contributor authored 52% of commits
13.5/13.5Contributor breadth49 contributors
10/10OpenSSF Scorecard: Contributorsproject has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled49
top_contributor_share0.523
How it's scored
24.4/42Issue resolution58% of issues closed
20.3/30PR acceptance82/121 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 6/9 approved changesets -- score normalized to 6
Inputs used
merged_prs82
open_issues55
closed_issues76
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.58
closed_unmerged_prs39
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 domainverified-domain status not read for this organization
21.4/25Owner reach946 followers of thephpleague
25/25Track record159 public repos, account ~15 yr old
Inputs used
followers946
owner_typeOrganization
is_verified
owner_loginthephpleague
public_repos159
account_age_days5,718
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 97 days ago
20/20Version history38 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesleague/openapi-psr7-validator
ecosystemspackagist
any_deprecatedno
min_days_since_publish97

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configphpcs.xml, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests4 out of 9 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

26At 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
1/2.5CI-Tests4 out of 9 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 6/9 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 9 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
3/7.5Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packagingno data
0/5Pinned-Dependenciesno data
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.1
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier26
security_posture_before_jurisdiction51
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

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.

36Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
14/40Legible commit history26 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.263
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpcs.xml, phpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.01
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/186 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes16,522
source_files_sampled186
oversized_source_files0

Key facts

562GitHub stars
49contributors
12commits, last 12 months
76days since last push
37releases
1bus factor
55open 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

More detail

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

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.

02040608010012010642019-092023-012026-05
Major 0Minor 0Patch 14

Each point covers 7 days.

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-08-13 21:21 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
4CI-Tests4 out of 9 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 6/9 approved changesets -- score normalized to 6
10Contributorsproject has 9 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
Packagistdevizzent/cebe-php-openapi^1.0composer.json
Packagistleague/uri^6.3 || ^7.0composer.json
Packagistpsr/cache^1.0 || ^2.0 || ^3.0composer.json
Packagistpsr/http-message^1.0 || ^2.0composer.json
Packagistpsr/http-server-middleware^1.0composer.json
Packagistrespect/validation^1.1.3 || ^2.0composer.json
Packagistriverline/multipart-parser^2.0.3composer.json
Packagistsymfony/polyfill-php80^1.27composer.json
Packagistwebmozart/assert^1.4 || ^2.0composer.json
All dependencies 20

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

RegistryPackageVersionRelation
Packagistdevizzent/cebe-php-openapidirect
Packagistleague/uridirect
Packagistpsr/cachedirect
Packagistpsr/http-messagedirect
Packagistpsr/http-server-middlewaredirect
Packagistrespect/validationdirect
Packagistriverline/multipart-parserdirect
Packagistsymfony/polyfill-php80direct
Packagistwebmozart/assertdirect
Packagistdoctrine/coding-standardindirect
Packagistext-jsonindirect
Packagistguzzlehttp/psr7indirect
Packagisthansott/psr7-cookiesindirect
Packagistphpindirect
Packagistphpstan/extension-installerindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistphpstan/phpstan-webmozart-assertindirect
Packagistphpunit/phpunitindirect
Packagistsymfony/cacheindirect
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.31.0 — full methodology · metrics wiki.

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