Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 20:43 UTC

pestphp / pest-plugin-stressless

Pest Stressless Plugin

PHPMIT★ 68 stars⑂ 7 forkssince Sep 2023View on GitHub ↗
KindLibraryPluginhow this is determined

pestphp/pest-plugin-stressless holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (69/100) and lowest on Vitality (46/100). It was last updated 32 days ago. A single contributor accounts for most of its recent work.

62
overall / 100
Moderate

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.

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

Ownership

PESTOrganization
458 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-stresslessv5.0.274,061932 days agoframeworkphptestingplugintestunitpest

Metrics by category

Vitality

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

46Weak · 21% of overall
How it's scored
18/36Push recencylast push 32 days ago
3.5/36Commit cadence5/52 weeks with commits
10.3/18Commit volume13 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_year13
human_commit_share0.98
days_since_last_push32
active_weeks_last_year5
How it's scored
27/27Ships releases3 releases published
0/36Release recencylatest release 1,004 days ago
27/27Release cadencea release every ~10.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv2.2.0
releases_from_tagsno
days_since_latest_release1,004
mean_days_between_releases10.8
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?

59Moderate · 17% of overall
How it's scored
29.6/60Stars68 stars
6.5/25Forks7 forks
5.3/15Watchers10 watchers
Inputs used
forks7
stars68
watchers10
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
64.9/80Monthly downloads74,061 downloads/month across packagist
8/20Registry dependents15 packages depend on it
Inputs used
packagespestphp/pest-plugin-stressless
dependents15
ecosystemspackagist
total_downloads1,179,672
monthly_downloads74,061
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
7.6/22.5Commit distributiontop contributor authored 66% of commits
8.1/13.5Contributor breadth6 contributors
10/10OpenSSF Scorecard: Contributorsproject has 16 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.661
How it's scored
0/42Issue resolutionno issues or no data
18.4/30PR acceptance19/31 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/23 approved changesets -- score normalized to 1
Inputs used
merged_prs19
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs12
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
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 domain
19.1/25Owner reach458 followers of pestphp
23.7/25Track record40 public repos, account ~6 yr old
Inputs used
followers458
owner_typeOrganization
is_verifiedno
owner_loginpestphp
public_repos40
account_age_days2,369

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 32 days ago
20/20Version history9 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespestphp/pest-plugin-stressless
ecosystemspackagist
any_deprecatedno
min_days_since_publish32

Engineering Quality

Are baseline engineering and documentation practices in place?

69Good · 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
8/20OpenSSF Scorecard: CI-Tests3 out of 7 merged PRs checked by a CI test -- score normalized to 4
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?

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1/2.5CI-Tests3 out of 7 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 4/23 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 16 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
1/5SASTSAST tool is not run on all commits -- score normalized to 2
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
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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://pestphp.com/llms.txt)
40/40Legible commit history76 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://pestphp.com/llms.txt
legible_history_share0.776
agent_instruction_files
agent_instruction_max_bytes
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 agent-authored commits among the last 100
8/8Automated maintenance2 of the last 100 commits are automated dependency updates
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
toolchain_manifests
dependency_bot_commit_share0.02
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/28 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes12,525
source_files_sampled28
oversized_source_files0

Key facts

68GitHub stars
6contributors
13commits, last 12 months
32days since last push
3releases
1bus factor
0open 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 ★ / 7 ⇿
0Stars
7Forks

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.

1234567712024-022025-052026-07

Each point covers 3 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-09-05 20:43 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
4CI-Tests3 out of 7 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/23 approved changesets -- score normalized to 1
10Contributorsproject has 16 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
2SASTSAST tool is not run on all commits -- score normalized to 2
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistpestphp/pest^5.0.3composer.json
Packagistpestphp/pest-plugin^5.0.0composer.json
All dependencies 6

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

RegistryPackageVersionRelation
Packagistpestphp/pestdirect
Packagistpestphp/pest-plugindirect
Packagistext-curlindirect
Packagistext-zipindirect
Packagistpestphp/pest-dev-toolsindirect
Packagistphpindirect
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.