Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 03:42 UTC

pushery / matomo-analytics-for-laravel

Privacy-first Matomo analytics for Laravel with cookieless tracking, reports, Web Vitals, batching and bot filtering.

PHPMIT★ 4 stars⑂ 0 forkssince Jun 2026View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

pushery/matomo-analytics-for-laravel holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Vitality (75/100) and lowest on Engineering Quality (34/100). It was last updated today. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

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.

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

Ownership

PUSHERYPersonal account
8 followers10 public repossince Mar 2026

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
6.2/36Commit cadence — 9/52 weeks with commits
15.3/18Commit volume — 49 commits in the last year
0/10OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year49
human_commit_share0.98
days_since_last_push0
active_weeks_last_year9

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 47 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count47
latest_release_tagv0.29.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1
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?

40Weak · 17% of overall
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars4
watchers0
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_badges10
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
46.9/80Monthly downloads — 3,293 downloads/month across packagist
2/20Registry dependents — 1 packages depend on it
Inputs used
packagespushery/matomo-analytics-for-laravel
dependents1
ecosystemspackagist
total_downloads6,926
monthly_downloads3,293
unverified_packages_excluded—

Sustainability & Governance

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

48Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
30/30PR acceptance — 47/47 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs47
open_issues0
closed_issues0
prs_merged_7d6
prs_decided_7d6
prs_merged_30d21
prs_decided_30d21
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
6.9/25Owner reach — 8 followers of pushery
8.5/25Track record — 10 public repos, account ~0 yr old
Inputs used
followers8
owner_typeUser
is_verified—
owner_loginpushery
public_repos10
account_age_days169
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 2 days ago
20/20Version history — 46 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespushery/matomo-analytics-for-laravel
ecosystemspackagist
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

34At Risk · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 20 topics
0/10Wiki
Inputs used
topicsanalytics, bot-protection, client-side-tracking, cookieless, gdpr, laravel, laravel-package, matomo, matomo-analytics, php, php-package, piwik, privacy, privacy-first, reporting-api, server-side-tracking, tracking, web-analytics, web-vitals, laravel-framework
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

46Weak · 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
0/2.5CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — project was created within the last 90 days. Please review its contents carefully
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.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/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
advisories0
affected_packages0
assessed_packages6
unassessed_packages37
affected_by_severitynone
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 6 resolved dependencies against OSV. 37 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.

40Weak · 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://docs.pushery.com/llms.txt)
40/40Legible commit history — 47 of 48 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.pushery.com/llms.txt
legible_history_share0.979
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
0/10Demonstrated agent practice — no agent-authored commits among the last 49
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no 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 code — PHP without a type-check config
55/55Manageable file sizes — 0/117 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes30,070
source_files_sampled117
oversized_source_files0

Key facts

4GitHub stars
1contributors
49commits, last 12 months
0days since last push
47releases
1bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

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

More detail

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-16 03:42 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 30 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 22
RegistryPackageVersion constraintManifest
Packagistguzzlehttp/guzzle^7.0 || ^8.0composer.json
Packagistilluminate/auth^12.0 || ^13.0composer.json
Packagistilluminate/bus^12.0 || ^13.0composer.json
Packagistilluminate/cache^12.0 || ^13.0composer.json
Packagistilluminate/config^12.0 || ^13.0composer.json
Packagistilluminate/console^12.0 || ^13.0composer.json
Packagistilluminate/contracts^12.0 || ^13.0composer.json
Packagistilluminate/cookie^12.0 || ^13.0composer.json
Packagistilluminate/database^12.0 || ^13.0composer.json
Packagistilluminate/events^12.0 || ^13.0composer.json
Packagistilluminate/http^12.0 || ^13.0composer.json
Packagistilluminate/log^12.0 || ^13.0composer.json
Packagistilluminate/queue^12.0 || ^13.0composer.json
Packagistilluminate/redis^12.0 || ^13.0composer.json
Packagistilluminate/routing^12.0 || ^13.0composer.json
Packagistilluminate/support^12.0 || ^13.0composer.json
Packagistilluminate/translation^12.0 || ^13.0composer.json
Packagistilluminate/view^12.0 || ^13.0composer.json
Packagistnesbot/carbon^3.0composer.json
Packagistsymfony/console^7.0 || ^8.0composer.json
Packagistsymfony/http-foundation^7.0 || ^8.0composer.json
Packagistsymfony/http-kernel^7.0 || ^8.0composer.json
All dependencies 43

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

RegistryPackageVersionRelation
Packagistguzzlehttp/guzzle—direct
Packagistilluminate/auth—direct
Packagistilluminate/bus—direct
Packagistilluminate/cache—direct
Packagistilluminate/config—direct
Packagistilluminate/console—direct
Packagistilluminate/contracts—direct
Packagistilluminate/cookie—direct
Packagistilluminate/database—direct
Packagistilluminate/events—direct
Packagistilluminate/http—direct
Packagistilluminate/log—direct
Packagistilluminate/queue—direct
Packagistilluminate/redis—direct
Packagistilluminate/routing—direct
Packagistilluminate/support—direct
Packagistilluminate/translation—direct
Packagistilluminate/view—direct
Packagistnesbot/carbon—direct
Packagistsymfony/console—direct
Packagistsymfony/http-foundation—direct
Packagistsymfony/http-kernel—direct
Packagistext-ctype—indirect
Packagistext-filter—indirect
Packagistext-hash—indirect
Packagistext-json—indirect
Packagistext-mbstring—indirect
Packagistlarastan/larastan3.11.0indirect
Packagistlaravel/pao—indirect
Packagistlaravel/pint—indirect
Packagistmatomo/device-detector—indirect
Packagistorchestra/testbench—indirect
Packagistpestphp/pest—indirect
Packagistpestphp/pest-plugin-agent—indirect
Packagistpestphp/pest-plugin-browser—indirect
Packagistpestphp/pest-plugin-laravel—indirect
Packagistpestphp/pest-plugin-phpstan5.2.1indirect
Packagistpestphp/pest-plugin-rector5.0.4indirect
Packagistpestphp/pest-plugin-type-coverage—indirect
Packagistphp—indirect
Packagistphpstan/phpstan2.2.13indirect
Packagistrector/rector2.6.6indirect
Packagistspaze/phpstan-disallowed-calls4.14.0indirect
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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.