Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 23:22 UTC

spatie / laravel-health

Check the health of your Laravel app

PHPMIT★ 886 stars⑂ 179 forkssince Nov 2021View on GitHub ↗

spatie/laravel-health holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (81/100) and lowest on AI Readiness (44/100). It was last updated 26 days ago. A single contributor accounts for most of its recent work.

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.

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)

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

Ownership

SpatieOrganization

3,845 followers529 public repossince May 2014

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
Packagist	spatie/laravel-health	1.40.2	860,149	156	36 days ago	laravel spatie laravel-health

Metrics by category

Vitality

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

81Excellent · 21% of overall

Development activity

69Good

How it's scored

28.8/36	Push recency — last push 26 days ago
15.2/36	Commit cadence — 22/52 weeks with commits
16.9/18	Commit volume — 76 commits in the last year
8/10	OpenSSF Scorecard: Maintained — 9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8

Inputs used

commits_last_year	76
human_commit_share	1
days_since_last_push	26
active_weeks_last_year	22

Release discipline

100Exceptional

How it's scored

27/27	Ships releases — 100 releases published
36/36	Release recency — latest release 36 days ago
27/27	Release cadence — a release every ~19.9 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	100
latest_release_tag	1.40.2
releases_from_tags	no
days_since_latest_release	36
mean_days_between_releases	19.9

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

Popularity & adoption

68Good

How it's scored

47.8/60	Stars — 886 stars
18.8/25	Forks — 179 forks
1.7/15	Watchers — 3 watchers

Inputs used

forks	179
stars	886
watchers	3
growth_state	organic
growth_factor_pct	100

Community health

70Good

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
18/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	4
has_contributing	yes
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	github.com, shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

92Excellent

How it's scored

79.1/80	Monthly downloads — 860,149 downloads/month across packagist
13.4/20	Registry dependents — 101 packages depend on it

Inputs used

packages	spatie/laravel-health
dependents	101
ecosystems	packagist
total_downloads	13,944,070
monthly_downloads	860,149
unverified_packages_excluded	—

Sustainability & Governance

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

69Good · 23% of overall

Maintainer resilience (bus factor)

39Weak

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
6.1/22.5	Commit distribution — top contributor authored 73% of commits
13.5/13.5	Contributor breadth — 100 contributors
10/10	OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	100
top_contributor_share	0.731

Issue & PR responsiveness

71Good

How it's scored

42/42	Issue resolution — 100% of issues closed
24.4/30	PR acceptance — 190/234 decided PRs merged
0/13	Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
4.5/15	OpenSSF Scorecard: Code-Review — Found 9/28 approved changesets -- score normalized to 3

Inputs used

merged_prs	190
open_issues	0
closed_issues	14
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	1
prs_decided_30d	2
issue_closed_ratio	1
closed_unmerged_prs	44
first_time_authors_30d	1
first_time_prs_merged_30d	0
first_time_prs_decided_30d	1

Ownership & stewardship

80Excellent

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
25/25	Owner reach — 3,845 followers of spatie
25/25	Track record — 529 public repos, account ~12 yr old

Inputs used

followers	3,845
owner_type	Organization
is_verified	no
owner_login	spatie
public_repos	529
account_age_days	4,509

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on packagist
35/35	Publish recency — latest publish 36 days ago
20/20	Version history — 156 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	spatie/laravel-health
ecosystems	packagist
any_deprecated	no
min_days_since_publish	36

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall

Engineering practices

66Good

How it's scored

24/24	CI workflows — 4 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
6.4/6.4	.editorconfig
12/20	OpenSSF Scorecard: CI-Tests — 9 out of 14 merged PRs checked by a CI test -- score normalized to 6

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	yes
has_linter_config	no
has_precommit_config	no

Documentation

80Excellent

How it's scored

30/30	README
25/25	Documentation directory
15/15	Documentation / homepage site — https://spatie.be/docs/laravel-health
10/10	Repository description
0/10	Topics
0/10	Wiki

Inputs used

topics	—
has_wiki	no
homepage	https://spatie.be/docs/laravel-health
docs_site	https://spatie.be/docs/laravel-health
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

46Weak · 16% of overall

Security posture

32At Risk

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
1.5/2.5	CI-Tests — 9 out of 14 merged PRs checked by a CI test -- score normalized to 6
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5	Code-Review — Found 9/28 approved changesets -- score normalized to 3
2.5/2.5	Contributors — project has 17 contributing companies or organizations
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
6/7.5	Maintained — 9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
0/7.5	Vulnerabilities — 14 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	13
scorecard_version	v5.5.0
checks_inconclusive	5
scorecard_aggregate	3.2

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	14
affected_packages	6
assessed_packages	108
unassessed_packages	29
affected_by_severity	high 4, moderate 2
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 108 resolved dependencies against OSV. 29 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

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

Agent context & guidance

38Weak

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15	Machine-readable docs (llms.txt) — llms.txt served by the project website (https://spatie.be/llms.txt)
23.5/40	Legible commit history — 44 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	yes
llms_txt_url	https://spatie.be/llms.txt
legible_history_share	0.44
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

44Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
0/11	Static type checking
10/10	Reproducible environment — lockfile
8/10	Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	yes
lockfiles	yarn.lock
has_dockerfile	no
typed_language	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0.04
toolchain_manifests	—
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

55Moderate

How it's scored

0/45	Type-checkable code — PHP without a type-check config
55/55	Manageable file sizes — 0/146 source files over 60KB

Inputs used

primary_language	PHP
largest_source_bytes	11,731
source_files_sampled	146
oversized_source_files	0

Key facts

886GitHub stars

100contributors

76commits, last 12 months

26days since last push

100releases

1bus factor

0open issues

npm, Packagistpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
Star history carried forward from 2026-07-19: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 886 stars today.

More detail

Star and fork history 879 ★ / 179 ⇿

879Stars

179Forks

100Releases

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.

Star history is shown as collected on 2026-07-19. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

Major 0Minor 32Patch 68

Each point covers 5 days.

OpenSSF Scorecard 3.2 / 10

3.2aggregate

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-12 23:21 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
6	CI-Tests	9 out of 14 merged PRs checked by a CI test -- score normalized to 6
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
3	Code-Review	Found 9/28 approved changesets -- score normalized to 3
10	Contributors	project has 17 contributing companies or organizations
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
8	Maintained	9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
0	Vulnerabilities	14 existing vulnerabilities detected

Direct dependencies 13

Registry	Package	Version constraint	Manifest
Packagist	dragonmantank/cron-expression	`^3.3.1`	composer.json
Packagist	guzzlehttp/guzzle	`^6.5\|^7.4.5\|^7.2\|^8.0`	composer.json
Packagist	illuminate/console	`^11.0\|^12.0\|^13.0`	composer.json
Packagist	illuminate/contracts	`^11.0\|^12.0\|^13.0`	composer.json
Packagist	illuminate/database	`^11.0\|^12.0\|^13.0`	composer.json
Packagist	illuminate/notifications	`^11.0\|^12.0\|^13.0`	composer.json
Packagist	illuminate/support	`^11.0\|^12.0\|^13.0`	composer.json
Packagist	laravel/serializable-closure	`^1.3\|^2.0`	composer.json
Packagist	nunomaduro/termwind	`^1.0\|^2.0`	composer.json
Packagist	spatie/enum	`^3.13`	composer.json
Packagist	spatie/laravel-package-tools	`^1.12.1`	composer.json
Packagist	spatie/regex	`^3.1.1\|^3.1`	composer.json
Packagist	symfony/process	`^5.4\|^6.0\|^7.0\|^8.0`	composer.json

All dependencies 137

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

Registry	Package	Version	Relation
Packagist	dragonmantank/cron-expression	`—`	direct
Packagist	guzzlehttp/guzzle	`—`	direct
Packagist	illuminate/console	`—`	direct
Packagist	illuminate/contracts	`—`	direct
Packagist	illuminate/database	`—`	direct
Packagist	illuminate/notifications	`—`	direct
Packagist	illuminate/support	`—`	direct
Packagist	laravel/serializable-closure	`—`	direct
Packagist	nunomaduro/termwind	`—`	direct
Packagist	spatie/enum	`—`	direct
Packagist	spatie/laravel-package-tools	`—`	direct
Packagist	spatie/regex	`—`	direct
Packagist	symfony/process	`—`	direct
npm	@alloc/quick-lru	`5.2.0`	indirect
npm	@isaacs/cliui	`8.0.2`	indirect
npm	@jridgewell/gen-mapping	`0.3.8`	indirect
npm	@jridgewell/resolve-uri	`3.1.2`	indirect
npm	@jridgewell/set-array	`1.2.1`	indirect
npm	@jridgewell/sourcemap-codec	`1.5.0`	indirect
npm	@jridgewell/trace-mapping	`0.3.25`	indirect
npm	@nodelib/fs.scandir	`2.1.5`	indirect
npm	@nodelib/fs.stat	`2.0.5`	indirect
npm	@nodelib/fs.walk	`1.2.8`	indirect
npm	@pkgjs/parseargs	`0.11.0`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.1.0`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	ansi-styles	`6.2.1`	indirect
npm	any-promise	`1.3.0`	indirect
npm	anymatch	`3.1.3`	indirect
npm	arg	`5.0.2`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	binary-extensions	`2.3.0`	indirect
npm	brace-expansion	`2.1.0`	indirect
npm	braces	`3.0.3`	indirect
npm	camelcase-css	`2.0.1`	indirect
npm	chokidar	`3.6.0`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	commander	`4.1.1`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	cssesc	`3.0.0`	indirect
npm	didyoumean	`1.2.2`	indirect
npm	dlv	`1.1.3`	indirect
npm	eastasianwidth	`0.2.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	emoji-regex	`9.2.2`	indirect
npm	fast-glob	`3.3.3`	indirect
npm	fastq	`1.19.1`	indirect
npm	fill-range	`7.1.1`	indirect
npm	foreground-child	`3.3.1`	indirect
npm	fsevents	`2.3.3`	indirect
npm	function-bind	`1.1.2`	indirect
npm	glob	`10.5.0`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	glob-parent	`6.0.2`	indirect
npm	hasown	`2.0.2`	indirect
npm	is-binary-path	`2.1.0`	indirect
npm	is-core-module	`2.16.1`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	jackspeak	`3.4.3`	indirect
npm	jiti	`1.21.7`	indirect
npm	lilconfig	`3.1.3`	indirect
npm	lines-and-columns	`1.2.4`	indirect
npm	lru-cache	`10.4.3`	indirect
npm	merge2	`1.4.1`	indirect
npm	micromatch	`4.0.8`	indirect
npm	minimatch	`9.0.9`	indirect
npm	minipass	`7.1.2`	indirect
npm	mz	`2.7.0`	indirect
npm	nanoid	`3.3.8`	indirect
npm	normalize-path	`3.0.0`	indirect
npm	object-assign	`4.1.1`	indirect
npm	object-hash	`3.0.0`	indirect
npm	package-json-from-dist	`1.0.1`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-parse	`1.0.7`	indirect
npm	path-scurry	`1.11.1`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`2.3.1`	indirect
npm	pify	`2.3.0`	indirect
npm	pirates	`4.0.6`	indirect
npm	postcss	`8.5.3`	indirect
npm	postcss-import	`15.1.0`	indirect
npm	postcss-js	`4.0.1`	indirect
npm	postcss-load-config	`4.0.2`	indirect
npm	postcss-nested	`6.2.0`	indirect
npm	postcss-selector-parser	`6.1.2`	indirect
npm	postcss-value-parser	`4.2.0`	indirect
npm	queue-microtask	`1.2.3`	indirect
npm	read-cache	`1.0.0`	indirect
npm	readdirp	`3.6.0`	indirect
npm	resolve	`1.22.10`	indirect
npm	reusify	`1.1.0`	indirect
npm	run-parallel	`1.2.0`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	source-map-js	`1.2.1`	indirect
npm	string-width	`4.2.3`	indirect
npm	string-width	`5.1.2`	indirect
npm	string-width-cjs	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-ansi	`7.1.0`	indirect
npm	strip-ansi-cjs	`6.0.1`	indirect
npm	sucrase	`3.35.0`	indirect
npm	supports-preserve-symlinks-flag	`1.0.0`	indirect
npm	tailwindcss	`3.4.17`	indirect
npm	thenify	`3.3.1`	indirect
npm	thenify-all	`1.6.0`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	ts-interface-checker	`0.1.13`	indirect
npm	util-deprecate	`1.0.2`	indirect
npm	which	`2.0.2`	indirect
npm	wrap-ansi	`8.1.0`	indirect
npm	wrap-ansi-cjs	`7.0.0`	indirect
npm	yaml	`2.7.0`	indirect
Packagist	larastan/larastan	`—`	indirect
Packagist	laravel/horizon	`—`	indirect
Packagist	nunomaduro/collision	`—`	indirect
Packagist	orchestra/testbench	`—`	indirect
Packagist	pestphp/pest	`—`	indirect
Packagist	pestphp/pest-plugin-laravel	`—`	indirect
Packagist	php	`—`	indirect
Packagist	phpstan/extension-installer	`—`	indirect
Packagist	phpstan/phpstan-deprecation-rules	`—`	indirect
Packagist	phpstan/phpstan-phpunit	`—`	indirect
Packagist	phpunit/phpunit	`—`	indirect
Packagist	spatie/laravel-ray	`—`	indirect
Packagist	spatie/pest-plugin-snapshots	`—`	indirect
Packagist	spatie/pest-plugin-test-time	`—`	indirect
Packagist	spatie/temporary-directory	`—`	indirect
Packagist	spatie/test-time	`—`	indirect

Dependency advisories 6

This repository publishes no package the index resolves, so its own dependency graph was assessed — 108 packages, which also include development and test pins that never ship: 6 carry known advisories, of which 0 are direct. 29 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

Package	Version	Relation	Severity	Advisories	Fixed in
brace-expansion	`2.1.0`	indirect	high	3	`5.0.9`
nanoid	`3.3.8`	indirect	high	3	`5.1.16`
picomatch	`2.3.1`	indirect	high	2	`4.0.4`
postcss	`8.5.3`	indirect	high	4	`8.5.23`
postcss-selector-parser	`6.1.2`	indirect	moderate	1	`7.1.3`
yaml	`2.7.0`	indirect	moderate	1	`2.8.3`

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records