Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-07 11:29 UTC

spatie / laravel-event-sourcing

The easiest way to get started with event sourcing in Laravel

PHPMIT★ 912 stars⑂ 177 forkssince Sep 2019View on GitHub ↗

spatie/laravel-event-sourcing holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (78/100) and lowest on AI Readiness (32/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

SpatieOrganization
3,813 followers525 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-event-sourcing7.15.0189,533116165 days agoeventaggregatesspatiesourcingprojectorsreactorslaravel-event-sourcing

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
6.2/36Commit cadence9/52 weeks with commits
14.8/18Commit volume43 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year43
human_commit_share1
days_since_last_push0
active_weeks_last_year9
How it's scored
27/27Ships releases100 releases published
27/36Release recencylatest release 165 days ago
27/27Release cadencea release every ~10.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tag7.15.0
releases_from_tagsno
days_since_latest_release165
mean_days_between_releases10.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?

74Good · 17% of overall
How it's scored
48/60Stars912 stars
18.7/25Forks177 forks
5.8/15Watchers12 watchers
Inputs used
forks177
stars912
watchers12
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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
70.4/80Monthly downloads189,533 downloads/month across packagist
10.3/20Registry dependents34 packages depend on it
Inputs used
packagesspatie/laravel-event-sourcing
dependents34
ecosystemspackagist
total_downloads4,578,369
monthly_downloads189,533
unverified_packages_excluded

Sustainability & Governance

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

78Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.9/22.5Commit distributiontop contributor authored 65% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 23 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.648
How it's scored
42/42Issue resolution100% of issues closed
24.5/30PR acceptance225/275 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 5/19 approved changesets -- score normalized to 2
Inputs used
merged_prs225
open_issues0
closed_issues125
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs50
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach3,813 followers of spatie
25/25Track record525 public repos, account ~12 yr old
Inputs used
followers3,813
owner_typeOrganization
is_verified
owner_loginspatie
public_repos525
account_age_days4,472
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 165 days ago
20/20Version history116 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesspatie/laravel-event-sourcing
ecosystemspackagist
any_deprecatedno
min_days_since_publish165

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests7 out of 10 merged PRs checked by a CI test -- score normalized to 7
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://docs.spatie.be/laravel-event-sourcing
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicsevent, sourcing, aggregate, projection, laravel, php
has_wikino
homepagehttps://docs.spatie.be/laravel-event-sourcing
docs_sitehttps://docs.spatie.be/laravel-event-sourcing
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

38Weak · 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
1.8/2.5CI-Tests7 out of 10 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 5/19 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 23 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): 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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
19.7/40Legible commit history37 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.37
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 practice5 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.05
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/176 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes16,946
source_files_sampled176
oversized_source_files0

Key facts

912GitHub stars
100contributors
43commits, last 12 months
0days since last push
100releases
1bus factor
0open issues
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 ★ / 177 ⇿
0Stars
177Forks
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.

0408012016020017662019-092023-022026-06
Major 4Minor 25Patch 71

Each point covers 7 days.

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-07 11:29 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
7CI-Tests7 out of 10 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 5/19 approved changesets -- score normalized to 2
10Contributorsproject has 23 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
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 13
RegistryPackageVersion constraintManifest
Packagistilluminate/console^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/database^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/events^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/support^10.0|^11.0|^12.0|^13.0composer.json
Packagistspatie/better-types^1.0composer.json
Packagistspatie/laravel-package-tools^1.19composer.json
Packagistspatie/php-attribute-reader^1.0composer.json
Packagistspatie/laravel-schemaless-attributes^2.5.1composer.json
Packagistsymfony/finder^6.0|^7.2.2|^8.0composer.json
Packagistsymfony/polyfill-php82>=1.31composer.json
Packagistsymfony/property-access^6.0|^7.2.3|^8.0composer.json
Packagistsymfony/property-info^6.0|^7.2.3|^8.0composer.json
Packagistsymfony/serializer^6.0|^7.2.3|^8.0composer.json
All dependencies 24

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

RegistryPackageVersionRelation
Packagistilluminate/consoledirect
Packagistilluminate/databasedirect
Packagistilluminate/eventsdirect
Packagistilluminate/supportdirect
Packagistspatie/better-typesdirect
Packagistspatie/laravel-package-toolsdirect
Packagistspatie/laravel-schemaless-attributesdirect
Packagistspatie/php-attribute-readerdirect
Packagistsymfony/finderdirect
Packagistsymfony/polyfill-php82direct
Packagistsymfony/property-accessdirect
Packagistsymfony/property-infodirect
Packagistsymfony/serializerdirect
Packagistext-jsonindirect
Packagistlaravel/horizonindirect
Packagistmockery/mockeryindirect
Packagistorchestra/testbenchindirect
Packagistpestphp/pestindirect
Packagistphpindirect
Packagistphpdocumentor/reflection-docblockindirect
Packagistphpunit/phpunitindirect
Packagistspatie/forkindirect
Packagistspatie/pest-plugin-snapshotsindirect
Packagistspatie/phpunit-snapshot-assertionsindirect
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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPackagist.