Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 01:58 UTC

spatie / laravel-pdf

Create PDF files in Laravel apps

PHPMIT★ 1,048 stars⑂ 107 forkssince Dec 2023View on GitHub ↗

spatie/laravel-pdf holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (89/100) and lowest on AI Readiness (51/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,845 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/laravel-pdf2.13.1749,2334411 days agolaravelspatielaravel-pdf

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
18/36Commit cadence — 26/52 weeks with commits
18/18Commit volume — 112 commits in the last year
10/10OpenSSF Scorecard: Maintained — 14 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year112
human_commit_share0.93
days_since_last_push4
active_weeks_last_year26

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 44 releases published
36/36Release recency — latest release 11 days ago
27/27Release cadence — a release every ~15.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count44
latest_release_tag2.13.1
releases_from_tagsno
days_since_latest_release11
mean_days_between_releases15.6
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
49/60Stars — 1,048 stars
16.9/25Forks — 107 forks
6.4/15Watchers — 15 watchers
Inputs used
forks107
stars1,048
watchers15
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.3/80Monthly downloads — 749,233 downloads/month across packagist
9.1/20Registry dependents — 22 packages depend on it
Inputs used
packagesspatie/laravel-pdf
dependents22
ecosystemspackagist
total_downloads6,467,430
monthly_downloads749,233
unverified_packages_excluded—

Sustainability & Governance

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

73Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.4/22.5Commit distribution — top contributor authored 72% of commits
13.5/13.5Contributor breadth — 50 contributors
10/10OpenSSF Scorecard: Contributors — project has 14 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled50
top_contributor_share0.715
How it's scored
42/42Issue resolution — 100% of issues closed
24.3/30PR acceptance — 94/116 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 10/27 approved changesets -- score normalized to 3
Inputs used
merged_prs94
open_issues0
closed_issues81
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio1
closed_unmerged_prs22
first_time_authors_30d2
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
25/25Owner reach — 3,845 followers of spatie
25/25Track record — 529 public repos, account ~12 yr old
Inputs used
followers3,845
owner_typeOrganization
is_verifiedno
owner_loginspatie
public_repos529
account_age_days4,509

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 10 out of 20 merged PRs checked by a CI test -- score normalized to 5
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 site — https://spatie.be/docs/laravel-pdf
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicslaravel, pdf, php
has_wikino
homepagehttps://spatie.be/docs/laravel-pdf
docs_sitehttps://spatie.be/docs/laravel-pdf
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 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
1.2/2.5CI-Tests — 10 out of 20 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 10/27 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 14 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
7.5/7.5Maintained — 14 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
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
0/7.5Vulnerabilities — 16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.4
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/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories16
affected_packages6
assessed_packages105
unassessed_packages29
affected_by_severitycritical 1, high 4, moderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 105 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.

51Moderate · 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)
26.4/40Legible commit history — 46 of 93 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.495
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
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 26 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 6 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.26
toolchain_manifests—
dependency_bot_commit_share0.06
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/87 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes20,215
source_files_sampled87
oversized_source_files0

Key facts

1,048GitHub stars
50contributors
112commits, last 12 months
4days since last push
44releases
1bus factor
0open issues
npm, Packagist, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 107 ⇿
0Stars
107Forks
44Releases

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.

02040608010012010642023-122025-052026-09
Major 2Minor 22Patch 20

Each point covers 3 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-13 01:58 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
5CI-Tests10 out of 20 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/27 approved changesets -- score normalized to 3
10Contributorsproject has 14 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained14 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
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
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
Packagistilluminate/contracts^11.0|^12.0|^13.0composer.json
Packagistspatie/laravel-package-tools^1.16.1composer.json
Packagistspatie/temporary-directory^2.2.1composer.json
npmpixelmatch^5.3.0package.json
npmpngjs^7.0.0package.json
npmpuppeteer^22.8.2package.json
All dependencies 134

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

RegistryPackageVersionRelation
npmpixelmatch5.3.0direct
npmpngjs6.0.0direct
npmpngjs7.0.0direct
npmpuppeteer22.15.0direct
Packagistilluminate/contracts—direct
Packagistspatie/laravel-package-tools—direct
Packagistspatie/temporary-directory—direct
npm@babel/code-frame7.27.1indirect
npm@babel/helper-validator-identifier7.27.1indirect
npm@puppeteer/browsers2.3.0indirect
npm@tootallnate/quickjs-emscripten0.23.0indirect
npm@types/node22.15.30indirect
npm@types/yauzl2.10.3indirect
npmagent-base7.1.3indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmast-types0.13.4indirect
npmb4a1.6.7indirect
npmbare-events2.5.4indirect
npmbare-fs4.1.5indirect
npmbare-os3.6.1indirect
npmbare-path3.0.0indirect
npmbare-stream2.6.5indirect
npmbase64-js1.5.1indirect
npmbasic-ftp5.0.5indirect
npmbuffer5.7.1indirect
npmbuffer-crc320.2.13indirect
npmcallsites3.1.0indirect
npmchromium-bidi0.6.3indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcosmiconfig9.0.0indirect
npmdata-uri-to-buffer6.0.2indirect
npmdebug4.4.1indirect
npmdegenerator5.0.1indirect
npmdevtools-protocol0.0.1312386indirect
npmemoji-regex8.0.0indirect
npmend-of-stream1.4.4indirect
npmenv-paths2.2.1indirect
npmerror-ex1.3.2indirect
npmescalade3.2.0indirect
npmescodegen2.1.0indirect
npmesprima4.0.1indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmextract-zip2.0.1indirect
npmfast-fifo1.3.2indirect
npmfd-slicer1.1.0indirect
npmget-caller-file2.0.5indirect
npmget-stream5.2.0indirect
npmget-uri6.0.4indirect
npmhttp-proxy-agent7.0.2indirect
npmhttps-proxy-agent7.0.6indirect
npmieee7541.2.1indirect
npmimport-fresh3.3.1indirect
npmip-address9.0.5indirect
npmis-arrayish0.2.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmjs-tokens4.0.0indirect
npmjs-yaml4.1.0indirect
npmjsbn1.1.0indirect
npmjson-parse-even-better-errors2.3.1indirect
npmlines-and-columns1.2.4indirect
npmlru-cache7.18.3indirect
npmmitt3.0.1indirect
npmms2.1.3indirect
npmnetmask2.0.2indirect
npmonce1.4.0indirect
npmpac-proxy-agent7.2.0indirect
npmpac-resolver7.0.1indirect
npmparent-module1.0.1indirect
npmparse-json5.2.0indirect
npmpend1.2.0indirect
npmpicocolors1.1.1indirect
npmprogress2.0.3indirect
npmproxy-agent6.5.0indirect
npmproxy-from-env1.1.0indirect
npmpump3.0.2indirect
npmpuppeteer-core22.15.0indirect
npmrequire-directory2.1.1indirect
npmresolve-from4.0.0indirect
npmsemver7.7.2indirect
npmsmart-buffer4.2.0indirect
npmsocks2.8.4indirect
npmsocks-proxy-agent8.0.5indirect
npmsource-map0.6.1indirect
npmsprintf-js1.1.3indirect
npmstreamx2.22.1indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmtar-fs3.0.9indirect
npmtar-stream3.1.7indirect
npmtext-decoder1.2.3indirect
npmthrough2.3.8indirect
npmtslib2.8.1indirect
npmunbzip2-stream1.4.3indirect
npmundici-types6.21.0indirect
npmurlpattern-polyfill10.0.0indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmws8.18.2indirect
npmy18n5.0.8indirect
npmyargs17.7.2indirect
npmyargs-parser21.1.1indirect
npmyauzl2.10.0indirect
npmzod3.23.8indirect
Packagistchrome-php/chrome—indirect
Packagistdompdf/dompdf—indirect
Packagistext-imagick—indirect
Packagistlarastan/larastan—indirect
Packagistlaravel/pint—indirect
Packagistnunomaduro/collision—indirect
Packagistorchestra/testbench—indirect
Packagistpestphp/pest—indirect
Packagistpestphp/pest-plugin-arch—indirect
Packagistpestphp/pest-plugin-laravel—indirect
Packagistphp—indirect
Packagistphpstan/extension-installer—indirect
Packagistphpstan/phpstan-deprecation-rules—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistpontedilana/php-weasyprint—indirect
Packagistspatie/image—indirect
Packagistspatie/invade—indirect
Packagistspatie/laravel-ray—indirect
Packagistspatie/pdf-to-image—indirect
Packagistspatie/pdf-to-text—indirect
Packagistspatie/pest-expectations—indirect
Packagistspatie/pest-plugin-snapshots—indirect
Packagistspatie/pixelmatch-php—indirect
Packagisttecnickcom/tc-lib-pdf-encrypt—indirect
Packagistwnx/sidecar-browsershot—indirect
PyPIweasyprint—indirect
Dependency advisories 6

This repository publishes no package the index resolves, so its own dependency graph was assessed — 105 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.

PackageVersionRelationSeverityAdvisoriesFixed in
basic-ftp5.0.5indirectcritical45.3.1
extract-zip2.0.1indirecthigh2—
js-yaml4.1.0indirecthigh54.3.2
tar-fs3.0.9indirecthigh13.1.1
ws8.18.2indirecthigh28.21.0
ip-address9.0.5indirectmoderate210.3.1

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.

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.