Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 15:25 UTC

thephpleague / config

Simple yet expressive schema-based configuration library for PHP apps

PHPBSD-3-Clause★ 567 stars⑂ 18 forkssince May 2021View on GitHub ↗

thephpleague/config holds a health index of 55 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (75/100) and lowest on AI Readiness (35/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

The League of Extraordinary PackagesOrganization · verified domain
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/configv1.2.013,064,97051354 days agoconfigurationschemaconfigarraydotnesteddot-access

Metrics by category

Vitality

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

44Weak · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
2.1/36Commit cadence3/52 weeks with commits
5.4/18Commit volume3 commits in the last year
0/10OpenSSF Scorecard: Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year3
human_commit_share0.831
days_since_last_push0
active_weeks_last_year3
How it's scored
27/27Ships releases5 releases published
0/36Release recencylatest release 1,354 days ago
12.6/27Release cadencea release every ~139.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count5
latest_release_tagv1.2.0
releases_from_tagsno
days_since_latest_release1,354
mean_days_between_releases139.8
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?

75Good · 17% of overall
How it's scored
44.7/60Stars567 stars
10.3/25Forks18 forks
3.3/15Watchers5 watchers
Inputs used
forks18
stars567
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (BSD-3-Clause)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges7
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads13,064,970 downloads/month across packagist
9.3/20Registry dependents24 packages depend on it
Inputs used
packagesleague/config
dependents24
ecosystemspackagist
total_downloads358,808,692
monthly_downloads13,064,970
unverified_packages_excluded

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.6/22.5Commit distributiontop contributor authored 80% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.797
How it's scored
42/42Issue resolution100% of issues closed
25.2/30PR acceptance26/31 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 2/16 approved changesets -- score normalized to 1
Inputs used
merged_prs26
open_issues0
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs5
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
20/20Verified domain
21.4/25Owner reach946 followers of thephpleague
25/25Track record159 public repos, account ~15 yr old
Inputs used
followers946
owner_typeOrganization
is_verifiedyes
owner_loginthephpleague
public_repos159
account_age_days5,731
How it's scored
25/25Published & resolvable1 package(s) on packagist
4/35Publish recencylatest publish 1,354 days ago
20/20Version history5 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesleague/config
ecosystemspackagist
any_deprecatedno
min_days_since_publish1,354

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests4 out of 17 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://config.thephpleague.com
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsconfiguration, config, schema, php, hacktoberfest
has_wikino
homepagehttps://config.thephpleague.com
docs_sitehttps://config.thephpleague.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

47Weak · 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-Tests4 out of 17 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.8/7.5Code-ReviewFound 2/16 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 5 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): Branch-Protection, 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 advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories13
affected_packages5
assessed_packages46
unassessed_packages8
affected_by_severityhigh 5
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 46 resolved dependencies against OSV. 8 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.

35Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
13/40Legible commit history18 of 74 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.243
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 environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 89
8/8Automated maintenance15 of the last 89 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.169
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/16 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes9,530
source_files_sampled16
oversized_source_files0

Key facts

567GitHub stars
7contributors
3commits, last 12 months
0days since last push
5releases
1bus factor
0open issues
Packagist, RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 18 ⇿
0Stars
18Forks
1Releases

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.

0481216201812021-082023-122026-03
Major 0Minor 1Patch 0

Each point covers 5 days.

OpenSSF Scorecard 3.4 / 10
3.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-08-27 15:24 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-Tests4 out of 17 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/16 approved changesets -- score normalized to 1
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 2
RegistryPackageVersion constraintManifest
Packagistdflydev/dot-access-data^3.0.1composer.json
Packagistnette/schema^1.2composer.json
All dependencies 54

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

RegistryPackageVersionRelation
Packagistdflydev/dot-access-datadirect
Packagistnette/schemadirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
Packagistscrutinizer/ocularindirect
Packagistunleashedtech/php-coding-standardindirect
Packagistvimeo/psalmindirect
RubyGemsaddressable2.8.7indirect
RubyGemscolorator1.1.0indirect
RubyGemsconcurrent-ruby1.2.3indirect
RubyGemsem-websocket0.5.3indirect
RubyGemseventmachine1.2.7indirect
RubyGemsfaraday1.10.3indirect
RubyGemsfaraday-em_http1.0.0indirect
RubyGemsfaraday-em_synchrony1.0.0indirect
RubyGemsfaraday-excon1.1.0indirect
RubyGemsfaraday-httpclient1.0.1indirect
RubyGemsfaraday-multipart1.0.4indirect
RubyGemsfaraday-net_http1.0.1indirect
RubyGemsfaraday-net_http_persistent1.2.0indirect
RubyGemsfaraday-patron1.0.0indirect
RubyGemsfaraday-rack1.0.0indirect
RubyGemsfaraday-retry1.0.3indirect
RubyGemsffi1.16.3indirect
RubyGemsforwardable-extended2.6.0indirect
RubyGemshttp_parser.rb0.8.0indirect
RubyGemsi18n1.14.6indirect
RubyGemsjekyll4.3.4indirect
RubyGemsjekyll-github-metadata2.16.1indirect
RubyGemsjekyll-redirect-from0.16.0indirect
RubyGemsjekyll-sass-converter2.2.0indirect
RubyGemsjekyll-watch2.2.1indirect
RubyGemskramdown2.4.0indirect
RubyGemskramdown-parser-gfm1.1.0indirect
RubyGemsliquid4.0.4indirect
RubyGemslisten3.8.0indirect
RubyGemsmercenary0.4.0indirect
RubyGemsmultipart-post2.3.0indirect
RubyGemsoctokit4.25.1indirect
RubyGemspathutil0.16.2indirect
RubyGemspublic_suffix4.0.7indirect
RubyGemsrb-fsevent0.11.2indirect
RubyGemsrb-inotify0.10.1indirect
RubyGemsrexml3.2.9indirect
RubyGemsrouge3.30.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemssafe_yaml1.0.5indirect
RubyGemssassc2.4.0indirect
RubyGemssawyer0.9.2indirect
RubyGemsstrscan3.1.0indirect
RubyGemsterminal-table1.8.0indirect
RubyGemsunicode-display_width1.8.0indirect
RubyGemswebrick1.8.1indirect
Dependency advisories 5

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

PackageVersionRelationSeverityAdvisoriesFixed in
addressable2.8.7indirecthigh12.9.0
concurrent-ruby1.2.3indirecthigh31.3.7
faraday1.10.3indirecthigh22.14.3
rexml3.2.9indirecthigh53.3.9
webrick1.8.1indirecthigh21.8.2

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