Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 10:21 UTC

spatie / phpunit-snapshot-assertions

A way to test without writing actual test cases

PHPMIT★ 698 stars⑂ 74 forkssince Dec 2016View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

spatie/phpunit-snapshot-assertions holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (77/100) and lowest on Security (43/100). It was last updated 80 days ago. 2 contributors account 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

SpatieOrganization
3,852 followers529 public repossince May 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistspatie/phpunit-snapshot-assertions5.4.0752,17772138 days agotestingphpunitsnapshotassertspatiephpunit-snapshot-assertions

Metrics by category

Vitality

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

58Moderate · 21% of overall
How it's scored
18/36Push recency — last push 80 days ago
9/36Commit cadence — 13/52 weeks with commits
15.3/18Commit volume — 50 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year50
human_commit_share0.77
days_since_last_push80
active_weeks_last_year13
How it's scored
27/27Ships releases — 70 releases published
27/36Release recency — latest release 138 days ago
19.8/27Release cadence — a release every ~56.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count70
latest_release_tag5.4.0
releases_from_tagsno
days_since_latest_release138
mean_days_between_releases56.2
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?

75Good · 17% of overall
How it's scored
46.1/60Stars — 698 stars
15.5/25Forks — 74 forks
4.7/15Watchers — 8 watchers
Inputs used
forks74
stars698
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
78.4/80Monthly downloads — 752,177 downloads/month across packagist
18.3/20Registry dependents — 550 packages depend on it
Inputs used
packagesspatie/phpunit-snapshot-assertions
dependents550
ecosystemspackagist
total_downloads21,533,328
monthly_downloads752,177
unverified_packages_excluded—

Sustainability & Governance

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

77Good · 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 — 56 contributors
10/10OpenSSF Scorecard: Contributors — project has 24 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled56
top_contributor_share0.419
How it's scored
42/42Issue resolution — 100% of issues closed
20.4/30PR acceptance — 122/179 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/18 approved changesets -- score normalized to 0
Inputs used
merged_prs122
open_issues0
closed_issues60
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs57
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
25/25Owner reach — 3,852 followers of spatie
25/25Track record — 529 public repos, account ~12 yr old
Inputs used
followers3,852
owner_typeOrganization
is_verifiedno
owner_loginspatie
public_repos529
account_age_days4,510

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 138 days ago
20/20Version history — 72 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesspatie/phpunit-snapshot-assertions
ecosystemspackagist
any_deprecatedno
min_days_since_publish138

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 6 out of 6 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://spatie.be/courses/testing-laravel-with-pest/snapshot-testing
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicsphpunit, testing, php, snapshot-testing
has_wikino
homepagehttps://spatie.be/courses/testing-laravel-with-pest/snapshot-testing
docs_sitehttps://spatie.be/courses/testing-laravel-with-pest/snapshot-testing
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

43Weak · 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.5/2.5CI-Tests — 6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/18 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 24 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): 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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://spatie.be/llms.txt)
23.5/40Legible commit history — 34 of 77 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://spatie.be/llms.txt
legible_history_share0.442
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice — 13 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 15 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.13
toolchain_manifests—
dependency_bot_commit_share0.15
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
55/55Manageable file sizes — 0/34 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes20,142
source_files_sampled34
oversized_source_files0
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 — example
Inputs used
example_dirsexample
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

698GitHub stars
56contributors
50commits, last 12 months
80days since last push
70releases
2bus factor
0open issues
npm, 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 ★ / 74 ⇿
0Stars
74Forks
66Releases

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.

01325385063757322017-012021-072026-01
Major 5Minor 14Patch 47

Each point covers 9 days.

OpenSSF Scorecard 4.3 / 10
4.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-09-14 10:20 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/18 approved changesets -- score normalized to 0
10Contributorsproject has 24 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Packagistsymfony/property-access^5.2|^6.2|^7.0|^8.0composer.json
Packagistsymfony/serializer^5.2|^6.2|^7.0|^8.0composer.json
Packagistsymfony/yaml^5.2|^6.2|^7.0|^8.0composer.json
npmpixelmatch^5.3.0package.json
npmpngjs^7.0.0package.json
All dependencies 14

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

RegistryPackageVersionRelation
npmpixelmatch^5.3.0direct
npmpngjs^7.0.0direct
Packagistsymfony/property-access—direct
Packagistsymfony/serializer—direct
Packagistsymfony/yaml—direct
Packagistcomposer-runtime-api—indirect
Packagistext-dom—indirect
Packagistext-json—indirect
Packagistext-libxml—indirect
Packagistphp—indirect
Packagistphpunit/phpunit—indirect
Packagistspatie/phpunit-snapshot-assertions—indirect
Packagistspatie/pixelmatch-php—indirect
Packagistspatie/ray—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.