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

phpspec / phpspec

SpecBDD Framework for PHP

PHP · GherkinCustom license★ 1,904 stars⑂ 286 forkssince Apr 2011View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

phpspec/phpspec holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (83/100) and lowest on Security (33/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

PHPSpec FrameworkOrganization
21 followers15 public repossince Sep 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistphpspec/phpspec9.0.0-rc.4.4250,5961372 days agotestingbddtddspectestsspecbddspecification

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
7.6/36Commit cadence — 11/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
2/10OpenSSF Scorecard: Maintained — 1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year30
human_commit_share1
days_since_last_push2
active_weeks_last_year11
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~9 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tag9.0.0-rc.4.4
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

79Good · 17% of overall
How it's scored
53.2/60Stars — 1,904 stars
20.5/25Forks — 286 forks
9.6/15Watchers — 55 watchers
Inputs used
forks286
stars1,904
watchers55
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_servicesgithub.com, poser.pugx.org, shields.io
has_pull_request_templateno
How it's scored
72/80Monthly downloads — 250,596 downloads/month across packagist
20/20Registry dependents — 3,780 packages depend on it
Inputs used
packagesphpspec/phpspec
dependents3,780
ecosystemspackagist
total_downloads38,372,100
monthly_downloads250,596
unverified_packages_excluded—

Sustainability & Governance

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

71Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.1/22.5Commit distribution — top contributor authored 42% of commits
13.5/13.5Contributor breadth — 100 contributors
10/10OpenSSF Scorecard: Contributors — project has 65 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled100
top_contributor_share0.416
How it's scored
33.1/42Issue resolution — 79% of issues closed
23.3/30PR acceptance — 758/975 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 4/11 approved changesets -- score normalized to 3
Inputs used
merged_prs758
open_issues135
closed_issues504
prs_merged_7d6
prs_decided_7d6
prs_merged_30d22
prs_decided_30d22
issue_closed_ratio0.789
closed_unmerged_prs217
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
0/20Verified domain
9.7/25Owner reach — 21 followers of phpspec
20.8/25Track record — 15 public repos, account ~16 yr old
Inputs used
followers21
owner_typeOrganization
is_verifiedno
owner_loginphpspec
public_repos15
account_age_days5,867

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 2 days ago
20/20Version history — 137 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesphpspec/phpspec
ecosystemspackagist
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

83Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 10 out of 11 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — http://www.phpspec.net
10/10Repository description
10/10Topics — 1 topics
10/10Wiki
Inputs used
topicshacktoberfest
has_wikiyes
homepagehttp://www.phpspec.net
docs_sitehttp://www.phpspec.net
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

33At Risk · 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/2.5CI-Tests — 10 out of 11 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 4/11 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 65 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
1.5/7.5Maintained — 1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, 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.

48Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
25.1/40Legible commit history — 47 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.47
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
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.9/55Manageable file sizes — 1/447 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes72,174
source_files_sampled447
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 — cookbook, example, examples
Inputs used
example_dirscookbook, example, examples
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

1,904GitHub stars
100contributors
30commits, last 12 months
2days since last push
100releases
2bus factor
135open issues
Packagist, PyPIpackage 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 ★ / 286 ⇿
0Stars
286Forks
73Releases

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.

05010015020025030028262011-072018-122026-04
Major 6Minor 21Patch 36

Each point covers 14 days.

OpenSSF Scorecard 3.3 / 10
3.3aggregate

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 10:11 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests10 out of 11 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 4/11 approved changesets -- score normalized to 3
10Contributorsproject has 65 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
2Maintained1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
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
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Packagistsebastian/exporter^3.1 || ^4.0 || ^5.0 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/console^5.4 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/event-dispatcher^5.4 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/process^5.4 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/finder^5.4 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/yaml^5.4 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistdoctrine/instantiator^1.3 || ^2composer.json
All dependencies 18

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

RegistryPackageVersionRelation
Packagistdoctrine/instantiator—direct
Packagistsebastian/exporter—direct
Packagistsymfony/console—direct
Packagistsymfony/event-dispatcher—direct
Packagistsymfony/finder—direct
Packagistsymfony/process—direct
Packagistsymfony/yaml—direct
Packagistbamarni/composer-bin-plugin—indirect
Packagistbehat/behat—indirect
Packagistext-tokenizer—indirect
Packagistphp—indirect
Packagistphpspec/php-diff—indirect
Packagistphpspec/prophecy—indirect
Packagistphpunit/phpunit—indirect
Packagistsymfony/filesystem—indirect
Packagistvimeo/psalm—indirect
PyPIsphinx—indirect
PyPIsphinxcontrib-phpdomain—indirect
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 statistics — Packagist.