Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 20:04 UTC

wmde / PsrLogTestDoubles

Test Doubles for the PSR-3 Logger Interface

PHPCustom license★ 7 stars⑂ 1 forksince Oct 2016View on GitHub ↗

wmde/PsrLogTestDoubles holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (79/100) and lowest on Community & Adoption (35/100). It was last updated 8 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

78 followers256 public repossince Mar 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistwmde/psr-log-test-doublesv3.4.03,7538447 days agologfixturestestfixturemocktest-doubletest-doublespsrpsr-3mocksspyspieslogger-spyloggerspy

Metrics by category

Vitality

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

61Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 8 days ago
22.2/36Commit cadence32/52 weeks with commits
15.1/18Commit volume47 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_year47
human_commit_share
days_since_last_push8
active_weeks_last_year32
How it's scored
27/27Ships releases3 releases published
7.2/36Release recencylatest release 447 days ago
5.4/27Release cadencea release every ~544 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv3.4.0
releases_from_tagsno
days_since_latest_release447
mean_days_between_releases544
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?

35Weak · 17% of overall
How it's scored
12.6/60Stars7 stars
0/25Forks1 forks
4.3/15Watchers7 watchers
Inputs used
forks1
stars7
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
47.7/80Monthly downloads3,753 downloads/month across packagist
5.2/20Registry dependents5 packages depend on it
Inputs used
packageswmde/psr-log-test-doubles
dependents5
ecosystemspackagist
total_downloads152,823
monthly_downloads3,753
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
25.2/54Bus factor2 contributor(s) cover half of all commits
13/22.5Commit distributiontop contributor authored 42% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 12 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled7
top_contributor_share0.421
How it's scored
42/42Issue resolution100% of issues closed
27.6/30PR acceptance80/87 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs80
open_issues0
closed_issues1
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs7
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance, OpenSSF Scorecard: Code-Review. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
13.6/25Owner reach78 followers of wmde
25/25Track record256 public repos, account ~15 yr old
Inputs used
followers78
owner_typeOrganization
is_verified
owner_loginwmde
public_repos256
account_age_days5,605
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on packagist
14/35Publish recencylatest publish 447 days ago
20/20Version history8 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageswmde/psr-log-test-doubles
ecosystemspackagist
any_deprecatedno
min_days_since_publish447

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/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_dirno
has_descriptionyes

Security

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

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 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
0/7.5Code-Reviewno data
2.5/2.5Contributorsproject has 12 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/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-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): Branch-Protection, Code-Review, Packaging, Signed-Releases. 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.

44Weak · 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
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configphpstan.neon
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
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. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/8 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes4,907
source_files_sampled8
oversized_source_files0

Key facts

7GitHub stars
7contributors
47commits, last 12 months
8days since last push
3releases
2bus factor
0open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-15 20:04 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
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
n/aCode-ReviewFound no human activity in the last 30 changesets
10Contributorsproject has 12 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistpsr/log~3.0composer.json
All dependencies 27

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

RegistryPackageVersionRelation
Packagistpsr/log3.0.2direct
Packagistmyclabs/deep-copy1.13.4indirect
Packagistnikic/php-parser5.7.0indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphpstan/phpstan2.2.5indirect
Packagistphpunit/php-code-coverage12.5.6indirect
Packagistphpunit/php-file-iterator6.0.1indirect
Packagistphpunit/php-invoker6.0.0indirect
Packagistphpunit/php-text-template5.0.0indirect
Packagistphpunit/php-timer8.0.0indirect
Packagistphpunit/phpunit12.5.22indirect
Packagistsebastian/cli-parser4.2.0indirect
Packagistsebastian/comparator7.1.6indirect
Packagistsebastian/complexity5.0.0indirect
Packagistsebastian/diff7.0.0indirect
Packagistsebastian/environment8.1.0indirect
Packagistsebastian/exporter7.0.2indirect
Packagistsebastian/global-state8.0.2indirect
Packagistsebastian/lines-of-code4.0.0indirect
Packagistsebastian/object-enumerator7.0.0indirect
Packagistsebastian/object-reflector5.0.0indirect
Packagistsebastian/recursion-context7.0.1indirect
Packagistsebastian/type6.0.3indirect
Packagistsebastian/version6.0.0indirect
Packagiststaabm/side-effects-detector1.0.5indirect
Packagisttheseer/tokenizer2.0.1indirect
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.