Login Audit Credits And Acknowledgements
Login Audit is part of the Capell package set. This page names the main frameworks, packages, authors, and services this package leans on, with a short note about what they make possible here. It is intentionally shorter than the repository-wide credits page and closer to the package itself.
Package role: Authentication log for Capell
Shared Foundations
Section titled “Shared Foundations”- Laravel, created by Taylor Otwell, gives this package routing, service providers, Eloquent, validation, queues, events, auth, caching, and the normal Laravel testing surface.
- Filament and the Filament project give this package admin resources, pages, widgets, forms, tables, actions, and panel integration.
- Composer, Packagist, and GitHub make the package install, split, and release workflow possible. Composer and Packagist deserve a special nod because Capell packages live and update through Composer metadata.
- Pest, Orchestra Testbench, PHPStan, Larastan, Laravel Pint, and Rector keep this package easier to test, review, and update when bugs are fixed.
Capell Packages Used Here
Section titled “Capell Packages Used Here”- Capell Admin supplies the Capell-side contracts, surfaces, or runtime that Login Audit builds on.
Open-source Packages And Authors
Section titled “Open-source Packages And Authors”- Rappasoft Laravel Authentication Log, by Anthony Rappa, records login, logout, and failed-login events so Capell can show access history without writing that storage layer from scratch.
- Tapp Network Filament Authentication Log, by Tapp Network, adds the Filament-facing authentication log UI that Capell can adapt for operators.
What We Especially Appreciate
Section titled “What We Especially Appreciate”Login Audit is useful because it turns authentication events into admin evidence. The package wraps recording, tables, widgets, and settings so access-related bug fixes are not scattered through the app.
Keeping This Page Current
Section titled “Keeping This Page Current”When Login Audit adds a new framework, service, or third-party package that becomes part of the user-facing workflow, update this page and the package README together. Credits should explain the practical help we get from a dependency, not just list a package name.