Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 11:57 UTC

spatie / image

https://spatie.be/docs/image/v3/introduction

PHPMIT★ 1,364 stars⑂ 139 forkssince Jan 2017View on GitHub ↗

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

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

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

Ownership

SpatieOrganization
3,824 followers526 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/image3.9.62,423,115974 days agoimagespatie

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
15.2/36Commit cadence22/52 weeks with commits
16.8/18Commit volume73 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_year73
human_commit_share0.8
days_since_last_push4
active_weeks_last_year22
How it's scored
27/27Ships releases95 releases published
36/36Release recencylatest release 4 days ago
19.8/27Release cadencea release every ~48.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count95
latest_release_tag3.9.6
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases48.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?

78Good · 17% of overall
How it's scored
50.8/60Stars1,364 stars
17.8/25Forks139 forks
6.5/15Watchers16 watchers
Inputs used
forks139
stars1,364
watchers16
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_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads2,423,115 downloads/month across packagist
14.3/20Registry dependents139 packages depend on it
Inputs used
packagesspatie/image
dependents139
ecosystemspackagist
total_downloads64,896,279
monthly_downloads2,423,115
unverified_packages_excluded

Sustainability & Governance

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

76Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.3/22.5Commit distributiontop contributor authored 54% of commits
13.5/13.5Contributor breadth80 contributors
10/10OpenSSF Scorecard: Contributorsproject has 24 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled80
top_contributor_share0.542
How it's scored
0/42Issue resolutionno issues or no data
26.6/30PR acceptance179/202 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 4/20 approved changesets -- score normalized to 2
Inputs used
merged_prs179
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio
closed_unmerged_prs23
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach3,824 followers of spatie
25/25Track record526 public repos, account ~12 yr old
Inputs used
followers3,824
owner_typeOrganization
is_verified
owner_loginspatie
public_repos526
account_age_days4,487
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 4 days ago
20/20Version history97 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesspatie/image
ecosystemspackagist
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://freek.dev/2619-new-major-versions-for-spatieimage-and-laravel-media-library-have-been-released
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsimage, php, imagick, gd
has_wikino
homepagehttps://freek.dev/2619-new-major-versions-for-spatieimage-and-laravel-media-library-have-been-released
docs_sitehttps://freek.dev/2619-new-major-versions-for-spatieimage-and-laravel-media-library-have-been-released
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

51Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests13 out of 13 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
1.5/7.5Code-ReviewFound 4/20 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 24 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
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-Dependenciesno data
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-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.1
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.

43Weak · 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://spatie.be/llms.txt)
22.7/40Legible commit history34 of 80 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.425
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
8/10Demonstrated agent practice4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance14 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_configno
typecheck_configs
agent_commit_share0.04
toolchain_manifests
dependency_bot_commit_share0.14
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/78 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes28,190
source_files_sampled78
oversized_source_files0

Key facts

1,364GitHub stars
80contributors
73commits, last 12 months
4days since last push
95releases
1bus 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 ★ / 139 ⇿
0Stars
139Forks
91Releases

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.

025507510012515013752017-022021-102026-06
Major 3Minor 21Patch 67

Each point covers 9 days.

OpenSSF Scorecard 5.1 / 10
5.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-08-22 11:57 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 4/20 approved changesets -- score normalized to 2
10Contributorsproject has 24 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
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
Packagistspatie/image-optimizer^1.7.5composer.json
Packagistspatie/temporary-directory^2.2composer.json
Packagistsymfony/process^6.4|^7.0|^8.0composer.json
npmpixelmatch^5.3.0package.json
npmpngjs^7.0.0package.json
All dependencies 20

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

RegistryPackageVersionRelation
npmpixelmatch^5.3.0direct
npmpngjs^7.0.0direct
Packagistspatie/image-optimizerdirect
Packagistspatie/temporary-directorydirect
Packagistsymfony/processdirect
Packagistext-exifindirect
Packagistext-ffiindirect
Packagistext-gdindirect
Packagistext-imagickindirect
Packagistext-jsonindirect
Packagistext-mbstringindirect
Packagistjcupitt/vipsindirect
Packagistlaravel/sailindirect
Packagistpestphp/pestindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistspatie/pest-plugin-snapshotsindirect
Packagistspatie/pixelmatch-phpindirect
Packagistspatie/rayindirect
Packagistsymfony/var-dumperindirect
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.