Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 11:52 UTC

thephpleague / flysystem

Abstraction for local and remote filesystems

PHPMIT★ 13,585 stars⑂ 861 forkssince Oct 2013View on GitHub ↗

thephpleague/flysystem holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (87/100) and lowest on AI Readiness (42/100). It was last updated 1 day ago. 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

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/flysystem3.35.215,094,50325646 days agofilefilesystemstorages3webdavcloudawsfilessftpftpfilesystems

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
12.5/36Commit cadence18/52 weeks with commits
15.3/18Commit volume50 commits in the last year
10/10OpenSSF Scorecard: Maintained19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year50
human_commit_share1
days_since_last_push1
active_weeks_last_year18
How it's scored
27/27Ships releases16 releases published
0/36Release recencylatest release 1,079 days ago
5.4/27Release cadencea release every ~389.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count16
latest_release_tag3.16.0
releases_from_tagsno
days_since_latest_release1,079
mean_days_between_releases389.4
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?

87Excellent · 17% of overall
How it's scored
60/60Stars13,585 stars
24.5/25Forks861 forks
12.2/15Watchers160 watchers
Inputs used
forks861
stars13,585
watchers160
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
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges7
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads15,094,503 downloads/month across packagist
20/20Registry dependents2,449 packages depend on it
Inputs used
packagesleague/flysystem
dependents2,449
ecosystemspackagist
total_downloads705,668,926
monthly_downloads15,094,503
unverified_packages_excluded

Sustainability & Governance

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

74Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.3/22.5Commit distributiontop contributor authored 81% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 48 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.811
How it's scored
38.3/42Issue resolution91% of issues closed
22.4/30PR acceptance691/924 decided PRs merged
8.7/13Newcomer PR acceptance2/3 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 10/21 approved changesets -- score normalized to 4
Inputs used
merged_prs691
open_issues85
closed_issues881
prs_merged_7d4
prs_decided_7d4
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio0.912
closed_unmerged_prs233
first_time_authors_30d3
first_time_prs_merged_30d2
first_time_prs_decided_30d3
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,726
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 46 days ago
20/20Version history256 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesleague/flysystem
ecosystemspackagist
any_deprecatedno
min_days_since_publish46

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.dist.php, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests7 out of 10 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://flysystem.thephpleague.com
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsfilesystem, php, thephpleague, filesystem-library
has_wikiyes
homepagehttps://flysystem.thephpleague.com
docs_sitehttps://flysystem.thephpleague.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.8/2.5CI-Tests7 out of 10 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 10/21 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 48 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
7.5/7.5Maintained19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file 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_aggregate6
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, 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.

42Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
26.1/40Legible commit history49 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.49
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.php-cs-fixer.dist.php, phpstan.neon
0/11Static type checking
10/10Reproducible environmentDockerfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.01
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 codePHP without a type-check config
55/55Manageable file sizes0/182 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes30,231
source_files_sampled182
oversized_source_files0

Key facts

13,585GitHub stars
100contributors
50commits, last 12 months
1days since last push
16releases
1bus factor
85open 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 ★ / 861 ⇿
0Stars
861Forks
16Releases

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.

02004006008001,00084592013-102020-032026-08
Major 1Minor 2Patch 13

Each point covers 12 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-22 11:52 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
7CI-Tests7 out of 10 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 10/21 approved changesets -- score normalized to 4
10Contributorsproject has 48 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistleague/flysystem-local^3.0.0composer.json
Packagistleague/mime-type-detection^1.0.0composer.json
All dependencies 21

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

RegistryPackageVersionRelation
Packagistleague/flysystem-localdirect
Packagistleague/mime-type-detectiondirect
Packagistasync-aws/s3indirect
Packagistasync-aws/simple-s3indirect
Packagistaws/aws-sdk-phpindirect
Packagistcomposer/semverindirect
Packagistext-fileinfoindirect
Packagistext-ftpindirect
Packagistext-mongodbindirect
Packagistext-zipindirect
Packagistfriendsofphp/php-cs-fixerindirect
Packagistgoogle/cloud-storageindirect
Packagistguzzlehttp/psr7indirect
Packagistleague/flysystemindirect
Packagistmicrosoft/azure-storage-blobindirect
Packagistmongodb/mongodbindirect
Packagistphpindirect
Packagistphpseclib/phpseclibindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
Packagistsabre/davindirect
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 statisticsPackagist.