Public record
Software health reportschema 0.13.0 · metrics 2.10.0 · 2026-07-18 16:42 UTC

pestphp / pest-plugin-browser

Pest Browser Plugin

PHPMIT★ 134 stars⑂ 125 forkssince Feb 2025View on GitHub ↗

pestphp/pest-plugin-browser holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (79/100) and lowest on AI Readiness (38/100). It was last updated today. 3 contributors account for most of its recent work.

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

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

Ownership

PESTOrganization
448 followers40 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-browserv4.3.1825,38110100 days agoframeworkphptestingtestbrowserunitpest

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
18/36Commit cadence26/52 weeks with commits
18/18Commit volume259 commits in the last year
4/10OpenSSF Scorecard: Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year259
human_commit_share
days_since_last_push0
active_weeks_last_year26
How it's scored
16.2/27Ships releases10 version tags (no GitHub releases)
27/36Release recencylatest release 100 days ago
27/27Release cadencea release every ~25.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count10
latest_release_tagv4.3.1
releases_from_tagsyes
days_since_latest_release100
mean_days_between_releases25.7
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
34.5/60Stars134 stars
17.4/25Forks125 forks
3.9/15Watchers6 watchers
Inputs used
forks125
stars134
watchers6
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
78.9/80Monthly downloads825,381 downloads/month across packagist
14.2/20Registry dependents136 packages depend on it
Inputs used
packagespestphp/pest-plugin-browser
dependents136
ecosystemspackagist
total_downloads4,207,048
monthly_downloads825,381
unverified_packages_excluded

Sustainability & Governance

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

79Good · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
14.4/22.5Commit distributiontop contributor authored 36% of commits
13.5/13.5Contributor breadth38 contributors
10/10OpenSSF Scorecard: Contributorsproject has 29 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled38
top_contributor_share0.359
How it's scored
0/42Issue resolutionno issues or no data
22.8/30PR acceptance132/174 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 6/22 approved changesets -- score normalized to 2
Inputs used
merged_prs132
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs42
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.7/25Track record40 public repos, account ~6 yr old
Inputs used
followers448
owner_typeOrganization
is_verified
owner_loginpestphp
public_repos40
account_age_days2,319
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 100 days ago
20/20Version history10 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespestphp/pest-plugin-browser
ecosystemspackagist
any_deprecatedno
min_days_since_publish100

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests4 out of 8 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.2/2.5CI-Tests4 out of 8 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 6/22 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 29 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
3/7.5Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packagingno data
0/5Pinned-Dependenciesno data
0.5/5SASTSAST tool is not run on all commits -- score normalized to 1
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.1
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.

38Weak · 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
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
54.6/55Manageable file sizes1/154 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes553,447
source_files_sampled154
oversized_source_files1

Key facts

134GitHub stars
38contributors
259commits, last 12 months
0days since last push
10releases
3bus factor
0open issues
npm, Packagistpackage ecosystems

More detail

OpenSSF Scorecard 6.1 / 10
6.1aggregate

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-18 16:42 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
5CI-Tests4 out of 8 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/22 approved changesets -- score normalized to 2
10Contributorsproject has 29 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
1SASTSAST tool is not run on all commits -- score normalized to 1
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Packagistamphp/amp^3.1.2composer.json
Packagistamphp/http-server^3.4.6composer.json
Packagistamphp/websocket-client^2.0.2composer.json
Packagistpestphp/pest^5.0.0composer.json
Packagistpestphp/pest-plugin^5.0.0composer.json
Packagistsymfony/process^8.1.0composer.json
npmplaywright^1.61.1package.json
All dependencies 17

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

RegistryPackageVersionRelation
npmplaywright1.61.1direct
Packagistamphp/ampdirect
Packagistamphp/http-serverdirect
Packagistamphp/websocket-clientdirect
Packagistpestphp/pestdirect
Packagistpestphp/pest-plugindirect
Packagistsymfony/processdirect
npmfsevents2.3.2indirect
npmplaywright-core1.61.1indirect
Packagistext-socketsindirect
Packagistlivewire/livewireindirect
Packagistnunomaduro/collisionindirect
Packagistorchestra/testbenchindirect
Packagistpestphp/pest-dev-toolsindirect
Packagistpestphp/pest-plugin-laravelindirect
Packagistpestphp/pest-plugin-type-coverageindirect
Packagistphpindirect
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.13.0 — full methodology · metrics wiki.

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