A simple, lightweight, and privacy-focused product analytics php package
AI Analysis
Pan is a lightweight, privacy-focused PHP analytics library designed for tracking user interactions (impressions, hovers, clicks) on specific DOM elements via a simple `data-pan` attribute, without collecting personal information. It is purpose-built for Laravel applications—particularly those using Inertia and Livewire—to measure engagement on individual UI components (tabs, buttons, popovers) rather than provide traditional cross-site tracking. Best suited for Laravel developers who need li...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Lightweight PHP analytics library for tracking UI interactions without personal data collection
Pan is a Laravel-focused PHP package for product analytics that tracks impressions, clicks, and hovers on HTML elements via simple data attributes. It prioritizes privacy by design—collecting no IP addresses or user agents—and integrates directly with Laravel, Livewire, and Inertia. Adoption appears limited to small-to-medium Laravel shops; real-world usage evidence is sparse. The project is actively maintained but has grown modestly since launch in October 2024.
Launched October 2024, Pan entered a market dominated by JavaScript-heavy analytics (Google Analytics, Mixpanel) and emerging self-hosted alternatives (Plausible, Fathom). It was designed specifically for Laravel developers seeking lightweight, privacy-preserving, in-app analytics without external dependencies or data collection concerns.
Pan gained 1,269 stars over ~9 months, averaging ~141 stars/month early on, then stabilizing to minimal weekly gains (1 star in final week before cutoff). Packagist downloads and fork activity (63 forks) suggest modest but genuine adoption. Growth appears tied to Laravel ecosystem enthusiasm rather than mainstream analytics adoption; the project has not demonstrated viral or sustained exponential growth patterns.
Adoption not verified. No case studies, user testimonials, or documented deployments mentioned in README. Packagist download badges are referenced but not shown in the truncated README. GitHub forks (63) and modest star growth suggest some real-world use, but scale and depth remain unclear.
Based on README: Pan is middleware-injected JavaScript library paired with Laravel backend. Likely uses a simple Eloquent model to store event records (impressions, clicks, hovers). Appears to support whitelisting analytics names and configurable database limits. No architectural details beyond 'lightweight' are documented.
CI workflow badge present (GitHub Actions), but specific test coverage percentage not documented in README. Test presence is signaled but depth is unknown.
Last push 2026-04-12 (approximately 3 months before analysis date). This indicates ongoing maintenance. Issue/PR velocity not visible from metadata alone; update frequency appears irregular rather than continuous, consistent with a stable, feature-complete tool receiving maintenance rather than active development.
ADOPT IF: you are a Laravel developer needing simple, privacy-preserving UI interaction tracking (tab views, button clicks, popover hovers) without external dependencies, external data transfer, or complex setup. AVOID IF: you require sophisticated segmentation, funnel analysis, cohort tracking, or cross-session user journeys—Pan is narrowly scoped to element-level events. MONITOR IF: you are considering it for a production Laravel app and want to verify adoption breadth and long-term maintenance; adoption evidence remains sparse as of mid-2026.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
3/10
- Adoption not verified: real-world production usage unclear; limited case study evidence.
- Narrow scope: only tracks impressions, clicks, hovers; no funnel analysis, user journeys, or retention metrics.
- Laravel-only: no framework-agnostic version; ecosystem lock-in to Laravel ecosystem.
- Reporting UI minimal: CLI-based output (`php artisan pan`) is functional but lacks sophisticated dashboarding or export options.
- Security model depends on admin discipline: whitelisting analytics names helps, but database-level abuse potential if misconfigured (50-record default limit is low but may require tuning).
Pan is likely to remain a stable, niche tool within the Laravel ecosystem. It may see modest adoption growth if Laravel developers increasingly reject SaaS analytics, but mainstream analytics adoption (by mid-market and enterprise) will likely remain with established platforms. The project appears to have found its intended audience and will probably enter a slow-growth or stable maintenance phase.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- PHP
- License
- MIT
- Last updated
- 3mo ago
- Created
- 21mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Top contributors
Recent releases
No releases published yet.
Similar repos
Openpanel-dev/openpanel
OpenPanel is an open-source analytics platform designed as a privacy-focused...
spatie/laravel-analytics
A Laravel package that integrates Google Analytics data retrieval into Laravel...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
1.3k | +1 | PHP | 7/10 | 3mo ago |
|
|
6.1k | — | TypeScript | 7/10 | 4d ago |
|
|
3.1k | — | PHP | 7/10 | 1mo ago |
|
|
3.2k | — | PHP | 8/10 | 2w ago |
|
|
2.8k | — | PHP | 6/10 | 2mo ago |
|
|
5.6k | — | PHP | 7/10 | 4d ago |
Official Laravel tool for app health/performance metrics. Broader scope; Pan is narrower, focused on user interaction tracking. Pulse likely has higher adoption within Laravel. Pan differentiates on privacy and simplicity for UI event tracking.
Self-hosted analytics platform with JavaScript SDK. Broader feature set and multi-language support. Openpanel requires external service; Pan is in-app and framework-integrated. Openpanel likely serves larger teams; Pan targets single-project Laravel shops.
Privacy-focused SaaS analytics. Require external account/data transfer. Pan avoids external dependencies and keeps data fully internal. Trade-off: Pan lacks sophisticated reporting UI that Plausible/Fathom provide.
Many Laravel apps build ad-hoc event tracking. Pan commoditizes this pattern. Adoption limited by: developers may already have bespoke solutions, or see custom code as simpler than adding a dependency.
Dominant, full-featured analytics. Pan serves users who reject these due to privacy concerns or who need only lightweight UI interaction tracking. Not a direct replacement; serves different value hierarchy.