Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 19:23 UTC

pestphp / pest-plugin-type-coverage

The Pest Type Coverage Plugin

PHPMIT★ 35 stars⑂ 18 forkssince May 2023View on GitHub ↗
KindLibraryPluginhow this is determined

pestphp/pest-plugin-type-coverage holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Engineering Quality (74/100) and lowest on AI Readiness (33/100). It was last updated 30 days ago. A single contributor accounts for most of its recent work.

75
overall / 100
Good

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.

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

Ownership

PESTOrganization
448 followers36 public repossince Mar 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistpestphp/pest-plugin-type-coveragev4.0.4406,57434101 days agoframeworkphptestingplugintestunitcoveragepesttype-coverage

Metrics by category

Vitality

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

64Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 30 days ago
6.2/36Commit cadence9/52 weeks with commits
12.6/18Commit volume24 commits in the last year
6/10OpenSSF Scorecard: Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year24
human_commit_share
days_since_last_push30
active_weeks_last_year9
How it's scored
16.2/27Ships releases34 version tags (no GitHub releases)
27/36Release recencylatest release 101 days ago
27/27Release cadencea release every ~43.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count34
latest_release_tagv4.0.4
releases_from_tagsyes
days_since_latest_release101
mean_days_between_releases43.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?

63Moderate · 17% of overall
How it's scored
24.8/60Stars35 stars
10.3/25Forks18 forks
1.7/15Watchers3 watchers
Inputs used
forks18
stars35
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
74.8/80Monthly downloads406,574 downloads/month across packagist
19.6/20Registry dependents860 packages depend on it
Inputs used
packagespestphp/pest-plugin-type-coverage
dependents860
ecosystemspackagist
total_downloads4,554,770
monthly_downloads406,574
unverified_packages_excluded

Sustainability & Governance

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

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.7/22.5Commit distributiontop contributor authored 70% of commits
13.5/13.5Contributor breadth16 contributors
10/10OpenSSF Scorecard: Contributorsproject has 23 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled16
top_contributor_share0.701
How it's scored
0/42Issue resolutionno issues or no data
21.1/30PR acceptance33/47 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/26 approved changesets -- score normalized to 0
Inputs used
merged_prs33
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs14
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
19.1/25Owner reach448 followers of pestphp
23.4/25Track record36 public repos, account ~6 yr old
Inputs used
followers448
owner_typeOrganization
is_verified
owner_loginpestphp
public_repos36
account_age_days2,317
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 101 days ago
20/20Version history34 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespestphp/pest-plugin-type-coverage
ecosystemspackagist
any_deprecatedno
min_days_since_publish101

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests4 out of 5 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://pestphp.com
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://pestphp.com
docs_sitehttps://pestphp.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests4 out of 5 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/26 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 23 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
4.5/7.5Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
0/5Packagingno data
0/5Pinned-Dependenciesno data
2/5SASTSAST tool is not run on all commits -- score normalized to 4
4.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.5
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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
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_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/19 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes9,278
source_files_sampled19
oversized_source_files0

Key facts

35GitHub stars
16contributors
24commits, last 12 months
30days since last push
34releases
1bus factor
0open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 6.5 / 10
6.5aggregate

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-07-16 19:23 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
8CI-Tests4 out of 5 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/26 approved changesets -- score normalized to 0
10Contributorsproject has 23 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
4SASTSAST tool is not run on all commits -- score normalized to 4
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
Packagistnunomaduro/pokio^1.0.0composer.json
Packagistpestphp/pest-plugin^4.0.0composer.json
Packagisttomasvotruba/type-coverage^1.0.0|^2.1.0composer.json
All dependencies 7

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

RegistryPackageVersionRelation
Packagistnunomaduro/pokiodirect
Packagistpestphp/pest-plugindirect
Packagisttomasvotruba/type-coveragedirect
Packagistpestphp/pestindirect
Packagistpestphp/pest-dev-toolsindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPackagist.