Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 23:39 UTC

php-testo / testo

The Testing Framework

PHPBSD-3-Clause★ 210 stars⑂ 14 forkssince Oct 2025View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

php-testo/testo holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on Security (60/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

php-testoOrganization
6 followers26 public repossince Oct 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagisttesto/testo0.10.4522,344646 days agotestingtesttestsdev

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
29.1/36Commit cadence42/52 weeks with commits
18/18Commit volume673 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year673
human_commit_share1
days_since_last_push0
active_weeks_last_year42

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 6 days ago
27/27Release cadencea release every ~0.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagbridge-symfony-console-0.1.11
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases0.6
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?

70Good · 17% of overall
How it's scored
37.6/60Stars210 stars
9.3/25Forks14 forks
1.7/15Watchers3 watchers
Inputs used
forks14
stars210
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges12
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateyes
How it's scored
58/80Monthly downloads22,344 downloads/month across packagist
14.6/20Registry dependents155 packages depend on it
Inputs used
packagestesto/testo
dependents155
ecosystemspackagist
total_downloads47,353
monthly_downloads22,344
unverified_packages_excluded

Sustainability & Governance

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

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.8/22.5Commit distributiontop contributor authored 92% of commits
13.5/13.5Contributor breadth14 contributors
10/10OpenSSF Scorecard: Contributorsproject has 24 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.921
How it's scored
26.3/42Issue resolution63% of issues closed
27.5/30PR acceptance228/249 decided PRs merged
13/13Newcomer PR acceptance6/6 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 6/19 approved changesets -- score normalized to 3
Inputs used
merged_prs228
open_issues22
closed_issues37
prs_merged_7d3
prs_decided_7d3
prs_merged_30d31
prs_decided_30d34
issue_closed_ratio0.627
closed_unmerged_prs21
first_time_authors_30d2
first_time_prs_merged_30d6
first_time_prs_decided_30d6
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
6.1/25Owner reach6 followers of php-testo
12.1/25Track record26 public repos, account ~0 yr old
Inputs used
followers6
owner_typeOrganization
is_verifiedno
owner_loginphp-testo
public_repos26
account_age_days314

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 6 days ago
20/20Version history64 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestesto/testo
ecosystemspackagist
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.dist.php
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://php-testo.github.io
10/10Repository description
10/10Topics1 topics
0/10Wiki
Inputs used
topicshacktoberfest
has_wikino
homepagehttps://php-testo.github.io
docs_sitehttps://php-testo.github.io
has_readmeyes
has_docs_diryes
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
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests12 out of 12 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
2.2/7.5Code-ReviewFound 6/19 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 24 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.5Maintained30 commit(s) and 14 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
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
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 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
advisories0
affected_packages0
assessed_packages1
unassessed_packages44
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 1 resolved dependencies against OSV. 44 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.

68Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://php-testo.github.io/llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://php-testo.github.io/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes5,508
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.php-cs-fixer.dist.php
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice12 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_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.12
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
54.9/55Manageable file sizes1/870 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes76,032
source_files_sampled870
oversized_source_files1

Key facts

210GitHub stars
14contributors
673commits, last 12 months
0days since last push
100releases
1bus factor
22open 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 ★ / 14 ⇿
0Stars
14Forks
98Releases

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.

03581013151412025-102026-032026-08
Major 0Minor 0Patch 26
OpenSSF Scorecard 5.0 / 10
5.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-09-05 23:39 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 6/19 approved changesets -- score normalized to 3
10Contributorsproject has 24 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 14 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 21
RegistryPackageVersion constraintManifest
Packagistinternal/destroy^1.0composer.json
Packagistinternal/path^1.3composer.json
Packagistpsr/container1 - 2composer.json
Packagistpsr/event-dispatcher^1.0composer.json
Packagistpsr/log^2.0 || ^3.0composer.json
Packagistsymfony/console^6.4 || ^7 || ^8.0composer.json
Packagistsymfony/finder^6.4 || ^7 || ^8.0composer.json
Packagisttesto/assert^0.1.14composer.json
Packagisttesto/fiber^0.1.3composer.json
Packagisttesto/bench^0.1.10composer.json
Packagisttesto/bridge-symfony-console^0.1.11composer.json
Packagisttesto/codecov^0.2.1composer.json
Packagisttesto/convention^0.1.4composer.json
Packagisttesto/data^0.1.9composer.json
Packagisttesto/filter^0.1.6composer.json
Packagisttesto/inline^0.1.8composer.json
Packagisttesto/lifecycle^0.1.5composer.json
Packagisttesto/repeat^0.1.9composer.json
Packagisttesto/retry^0.1.5composer.json
Packagisttesto/test^0.1.6composer.json
Packagistyiisoft/injector^1.2composer.json
All dependencies 45

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

RegistryPackageVersionRelation
Packagistinternal/destroydirect
Packagistinternal/pathdirect
Packagistpsr/containerdirect
Packagistpsr/event-dispatcherdirect
Packagistpsr/logdirect
Packagistsymfony/consoledirect
Packagistsymfony/finderdirect
Packagisttesto/assertdirect
Packagisttesto/benchdirect
Packagisttesto/bridge-symfony-consoledirect
Packagisttesto/codecovdirect
Packagisttesto/conventiondirect
Packagisttesto/datadirect
Packagisttesto/fiberdirect
Packagisttesto/filterdirect
Packagisttesto/inlinedirect
Packagisttesto/lifecycledirect
Packagisttesto/repeatdirect
Packagisttesto/retrydirect
Packagisttesto/testdirect
Packagistyiisoft/injectordirect
Packagistbamarni/composer-bin-pluginindirect
Packagistbuggregator/trapindirect
Packagistext-tokenizerindirect
Packagistext-xmlwriterindirect
Packagistinfection/abstract-testframework-adapterindirect
Packagistinfection/include-interceptorindirect
Packagistinfection/infectionindirect
Packagistllm/skillsindirect
Packagistmockery/mockeryindirect
Packagistphpindirect
Packagistphp-vcr/php-vcrindirect
Packagistphpunit/phpunitindirect
Packagistrector/rectorindirect
Packagistrevolt/event-loopindirect
Packagistroxblnfk/unpoly1.8.2indirect
Packagistspiral/code-styleindirect
Packagisttesto/bridge-infectionindirect
Packagisttesto/bridge-mockeryindirect
Packagisttesto/bridge-rectorindirect
Packagisttesto/bridge-revoltindirect
Packagisttesto/bridge-vcrindirect
Packagisttesto/facadeindirect
Packagisttesto/testoindirect
Packagistvimeo/psalmindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 44 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 statisticsPackagist.