PHPackages                             joshhanley/livewire-checksum-logger - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Debugging & Profiling](/categories/debugging)
4. /
5. joshhanley/livewire-checksum-logger

ActiveLibrary[Debugging & Profiling](/categories/debugging)

joshhanley/livewire-checksum-logger
===================================

An checksum logger for Livewire to debug corruption issues

v0.0.3(4y ago)64681MITPHPPHP ^7.4|^8.0

Since Aug 4Pushed 4y ago1 watchersCompare

[ Source](https://github.com/joshhanley/livewire-checksum-logger)[ Packagist](https://packagist.org/packages/joshhanley/livewire-checksum-logger)[ RSS](/packages/joshhanley-livewire-checksum-logger/feed)WikiDiscussions main Synced 3w ago

READMEChangelog (3)Dependencies (3)Versions (4)Used By (0)

Livewire Checksum Logger
========================

[](#livewire-checksum-logger)

This package dumps Livewire's fingerprint and memo data to a log channel for debugging the "Livewire encountered corrupt data" error.

Installation
------------

[](#installation)

To install the package run

```
composer require joshhanley/livewire-checksum-logger
```

Usage
-----

[](#usage)

In your `.env` file, set the below option to true to enable and false to disable (or remove)

```
LIVEWIRE_CHECKSUM_LOGGER_ENABLED=true

```

You can also specify which channel the package will use. Currently it will use Laravel's `log` by default, but also has support for `ray`

```
LIVEWIRE_CHECKSUM_LOGGER_CHANNEL=ray

```

Once your env variables have been configured, make an initial request that contains a Livewire component. You should see the Livewire component ID and "RESPONSE" with the fingerprint and memo payloads.

Then trigger a Livewire request, and you should see the Livewire component ID and "REQUEST" with the fingerprint and memo payloads.

You can then manually compare these to see if there are any differences.

Here is a sample of how it looks in ray:

[![ray example](https://raw.githubusercontent.com/joshhanley/livewire-checksum-logger/main/images/ray-example.png)](https://raw.githubusercontent.com/joshhanley/livewire-checksum-logger/main/images/ray-example.png)

And sample log output:

[![log example](https://raw.githubusercontent.com/joshhanley/livewire-checksum-logger/main/images/log-example.png)](https://raw.githubusercontent.com/joshhanley/livewire-checksum-logger/main/images/log-example.png)

###  Health Score

27

—

LowBetter than 47% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity19

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity48

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 85.7% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~104 days

Total

3

Last Release

1586d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/e4ad7053094ebecf63993d76e363d37d39ad322351abb57bdf1727f39222ea68?d=identicon)[joshhanley](/maintainers/joshhanley)

---

Top Contributors

[![joshhanley](https://avatars.githubusercontent.com/u/882837?v=4)](https://github.com/joshhanley "joshhanley (6 commits)")[![Qirel](https://avatars.githubusercontent.com/u/16939228?v=4)](https://github.com/Qirel "Qirel (1 commits)")

### Embed Badge

![Health badge](/badges/joshhanley-livewire-checksum-logger/health.svg)

```
[![Health](https://phpackages.com/badges/joshhanley-livewire-checksum-logger/health.svg)](https://phpackages.com/packages/joshhanley-livewire-checksum-logger)
```

###  Alternatives

[laravel/pulse

Laravel Pulse is a real-time application performance monitoring tool and dashboard for your Laravel application.

1.7k15.1M132](/packages/laravel-pulse)[psalm/plugin-laravel

Psalm plugin for Laravel

3355.3M346](/packages/psalm-plugin-laravel)[tallstackui/tallstackui

TallStackUI is a powerful suite of Blade components that elevate your workflow of Livewire applications.

725173.2k14](/packages/tallstackui-tallstackui)[mike-bronner/laravel-model-caching

Automatic caching for Eloquent models.

2.4k91.9k1](/packages/mike-bronner-laravel-model-caching)[illuminate/auth

The Illuminate Auth package.

10528.2M1.2k](/packages/illuminate-auth)[illuminate/routing

The Illuminate Routing package.

1419.2M3.0k](/packages/illuminate-routing)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)