Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 18:16 UTC

spatie / flare-client-php

Send PHP errors to Flare

PHPMIT★ 178 stars⑂ 21 forkssince May 2021View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

spatie/flare-client-php holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Security (43/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

SpatieOrganization
3,830 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/flare-client-php3.3.15,020,5858036 days agoexceptionreportingflarespatie

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
21.5/36Commit cadence31/52 weeks with commits
18/18Commit volume230 commits in the last year
10/10OpenSSF Scorecard: Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year230
human_commit_share1
days_since_last_push0
active_weeks_last_year31

Release discipline

100Exceptional
How it's scored
27/27Ships releases81 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~10.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count81
latest_release_tag3.4.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases10.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?

65Good · 17% of overall
How it's scored
36.5/60Stars178 stars
10.8/25Forks21 forks
0/15Watchers2 watchers
Inputs used
forks21
stars178
watchers2
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 downloads5,020,585 downloads/month across packagist
8/20Registry dependents15 packages depend on it
Inputs used
packagesspatie/flare-client-php
dependents15
ecosystemspackagist
total_downloads170,751,218
monthly_downloads5,020,585
unverified_packages_excluded

Sustainability & Governance

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

72Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.9/22.5Commit distributiontop contributor authored 60% of commits
13.5/13.5Contributor breadth23 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled23
top_contributor_share0.603
How it's scored
42/42Issue resolution100% of issues closed
25.5/30PR acceptance57/67 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/27 approved changesets -- score normalized to 0
Inputs used
merged_prs57
open_issues0
closed_issues17
prs_merged_7d3
prs_decided_7d3
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio1
closed_unmerged_prs10
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 backingorganization-owned
0/20Verified domain
25/25Owner reach3,830 followers of spatie
25/25Track record526 public repos, account ~12 yr old
Inputs used
followers3,830
owner_typeOrganization
is_verifiedno
owner_loginspatie
public_repos526
account_age_days4,493

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 36 days ago
20/20Version history80 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesspatie/flare-client-php
ecosystemspackagist
any_deprecatedno
min_days_since_publish36

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows4 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://flareapp.io/docs
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsphp, errors, flare
has_wikino
homepagehttps://flareapp.io/docs
docs_sitehttps://flareapp.io/docs
has_readmeyes
has_docs_diryes
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-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
0/7.5Code-ReviewFound 1/27 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 5 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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_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.

45Weak · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.MD, scripts/ralph/CLAUDE.md
0/15Machine-readable docs (llms.txt)
24/40Legible commit history45 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.45
agent_instruction_filesCLAUDE.MD, scripts/ralph/CLAUDE.md
agent_instruction_max_bytes4,079
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
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
toolchain_manifests
dependency_bot_commit_share0
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/266 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes27,735
source_files_sampled266
oversized_source_files0

Key facts

178GitHub stars
23contributors
230commits, last 12 months
0days since last push
81releases
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 ★ / 21 ⇿
0Stars
21Forks
68Releases

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.

048121620242122022-022024-042026-07
Major 2Minor 23Patch 40

Each point covers 5 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-08-27 18:15 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
0Code-ReviewFound 1/27 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 0 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
Packagistguzzlehttp/guzzle^7.9|^8.0composer.json
Packagistmonolog/monolog^3.0composer.json
Packagistpsr/container^2.0composer.json
Packagistspatie/backtrace^1.8.0composer.json
Packagistsymfony/console^5.2|^6.0|^7.0|^8.0composer.json
Packagistspatie/flare-daemon^0.3composer.json
Packagistsymfony/http-foundation^5.2|^6.0|^7.0|^8.0composer.json
Packagistsymfony/mime^5.2|^6.0|^7.0|^8.0composer.json
Packagistsymfony/process^5.2|^6.0|^7.0|^8.0composer.json
Packagistsymfony/var-dumper^5.2|^6.0|^7.0|^8.0composer.json
All dependencies 20

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

RegistryPackageVersionRelation
Packagistguzzlehttp/guzzledirect
Packagistmonolog/monologdirect
Packagistpsr/containerdirect
Packagistspatie/backtracedirect
Packagistspatie/flare-daemondirect
Packagistsymfony/consoledirect
Packagistsymfony/http-foundationdirect
Packagistsymfony/mimedirect
Packagistsymfony/processdirect
Packagistsymfony/var-dumperdirect
Packagistext-curlindirect
Packagistfriendsofphp/php-cs-fixerindirect
Packagistpestphp/pestindirect
Packagistphpindirect
Packagistphpstan/extension-installerindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-deprecation-rulesindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistspatie/invadeindirect
Packagistspatie/pest-plugin-snapshotsindirect
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.