Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 04:27 UTC

thephpleague / oauth2-server

A spec compliant, secure by default PHP OAuth 2.0 Server

PHPMIT★ 6,670 stars⑂ 1,134 forkssince Jun 2012View on GitHub ↗

thephpleague/oauth2-server holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (93/100) and lowest on AI Readiness (44/100). It was last updated today. A single contributor accounts for most of its recent work.

84
overall / 100
Excellent

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.

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

Ownership

The League of Extraordinary PackagesOrganization · verified domain
956 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/oauth2-server9.4.17,070,662116116 days agoauthorizationapiauthenticationoauthoauth2serverauthoauth-2.0secureresourceprotectauthorisationoauth-2

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
8.3/36Commit cadence — 12/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
3/10OpenSSF Scorecard: Maintained — 2 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year30
human_commit_share1
days_since_last_push0
active_weeks_last_year12
How it's scored
27/27Ships releases — 88 releases published
27/36Release recency — latest release 116 days ago
19.8/27Release cadence — a release every ~91.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count88
latest_release_tag9.4.1
releases_from_tagsno
days_since_latest_release116
mean_days_between_releases91.1
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?

93Exceptional · 17% of overall
How it's scored
60/60Stars — 6,670 stars
25/25Forks — 1,134 forks
12.8/15Watchers — 200 watchers
Inputs used
forks1,134
stars6,670
watchers200
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 7,070,662 downloads/month across packagist
16.7/20Registry dependents — 320 packages depend on it
Inputs used
packagesleague/oauth2-server
dependents320
ecosystemspackagist
total_downloads167,076,694
monthly_downloads7,070,662
unverified_packages_excluded—

Sustainability & Governance

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

76Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.1/22.5Commit distribution — top contributor authored 55% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 60 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled98
top_contributor_share0.552
How it's scored
39/42Issue resolution — 93% of issues closed
18.9/30PR acceptance — 461/733 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 8/14 approved changesets -- score normalized to 5
Inputs used
merged_prs461
open_issues54
closed_issues706
prs_merged_7d2
prs_decided_7d2
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.929
closed_unmerged_prs272
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 backing — organization-owned
20/20Verified domain
21.4/25Owner reach — 956 followers of thephpleague
25/25Track record — 159 public repos, account ~15 yr old
Inputs used
followers956
owner_typeOrganization
is_verifiedyes
owner_loginthephpleague
public_repos159
account_age_days5,785

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 116 days ago
20/20Version history — 116 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesleague/oauth2-server
ecosystemspackagist
any_deprecatedno
min_days_since_publish116

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 8 out of 9 merged PRs checked by a CI test -- score normalized to 8
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://oauth2.thephpleague.com
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicsoauth2, oauth2-server, oauth, php
has_wikino
homepagehttps://oauth2.thephpleague.com
docs_sitehttps://oauth2.thephpleague.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2/2.5CI-Tests — 8 out of 9 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 8/14 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 60 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
2.2/7.5Maintained — 2 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 3
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages14
unassessed_packages22
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 14 resolved dependencies against OSV. 22 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
13.9/40Legible commit history — 26 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.26
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
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
54.5/55Manageable file sizes — 1/118 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes108,611
source_files_sampled118
oversized_source_files1
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

6,670GitHub stars
98contributors
30commits, last 12 months
0days since last push
88releases
1bus factor
54open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 1,134 ⇿
0Stars
1,134Forks
74Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

02004006008001,0001,2001,134112014-062020-082026-10
Major 6Minor 16Patch 49

Each point covers 12 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-10-20 04:27 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests8 out of 9 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 8/14 approved changesets -- score normalized to 5
10Contributorsproject has 60 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained2 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 3
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 7
RegistryPackageVersion constraintManifest
Packagistleague/event^3.0composer.json
Packagistleague/uri^7.8composer.json
Packagistlcobucci/jwt^5.6composer.json
Packagistpsr/http-message^2.0composer.json
Packagistdefuse/php-encryption^2.4composer.json
Packagistpsr/http-server-middleware^1.0composer.json
Packagistpsr/clock^1.0composer.json
All dependencies 36

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

RegistryPackageVersionRelation
Packagistdefuse/php-encryption—direct
Packagistdefuse/php-encryption2.4.0direct
Packagistlcobucci/jwt—direct
Packagistlcobucci/jwt4.3.0direct
Packagistleague/event—direct
Packagistleague/event3.0.2direct
Packagistleague/uri—direct
Packagistpsr/clock—direct
Packagistpsr/clock1.0.0direct
Packagistpsr/http-message—direct
Packagistpsr/http-message1.1direct
Packagistpsr/http-server-middleware—direct
Packagistext-json—indirect
Packagistext-openssl—indirect
Packagistlaminas/laminas-diactoros—indirect
Packagistlaminas/laminas-diactoros2.26.0indirect
Packagistlcobucci/clock3.0.0indirect
Packagistnikic/fast-route1.3.0indirect
Packagistparagonie/random_compat—indirect
Packagistparagonie/random_compat9.99.100indirect
Packagistphp—indirect
Packagistphp-parallel-lint/php-parallel-lint—indirect
Packagistphpstan/extension-installer—indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-deprecation-rules—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistphpstan/phpstan-strict-rules—indirect
Packagistphpunit/phpunit—indirect
Packagistpimple/pimple3.5.0indirect
Packagistpsr/container1.1.2indirect
Packagistpsr/event-dispatcher1.0.0indirect
Packagistpsr/http-factory1.0.2indirect
Packagistroave/security-advisories—indirect
Packagistslevomat/coding-standard—indirect
Packagistslim/slim3.12.5indirect
Packagistsquizlabs/php_codesniffer—indirect
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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