Login Audit
Login Audit keeps a clear Capell access history: logins, failed attempts, logouts, devices, and sessions.
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.0.32 Sep 2, 2026
- Recent activity
- 3 approved releases in the last 12 months
What Login Audit helps you do
See the admin screens, public surfaces, migrations, and retained data this adds before you install.
This installs as an ordinary Composer package. Remove it with Composer whenever you want; uninstalling leaves your content in place.
Active Capell Membership access covers the curated Released catalogue and lets the account opt into Beta extensions after reviewing their risk.
The demo site runs the full Capell catalogue.
Priority support is included with Capell Membership or any paid licence.
composer require capell-app/login-audit
- Version
- 1.0.32
- Runs on
- Capell 1.x, Laravel 12.41.1+ in the 12.x line or Laravel 13.x, PHP 8.4.
- Last release
- Sep 2, 2026
- Support
- Priority support
- Data access
- Uses package-local configuration and Capell metadata needed to enable the feature.
- Documentation
- Documentation
Login Audit keeps a clear Capell access history: logins, failed attempts, logouts, devices, and sessions.
Admins can review account activity for support cases and security investigations without piecing together server logs.
Retention controls keep audit data useful without storing it forever by default.
Use it when Capell needs accountable authentication history close to the users and roles it describes.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Login Audit adds when enabled.
- Audit
- Authentication
- Operations
Install with confidence.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
- Support
- priority
- Data access
- Uses package-local configuration and Capell metadata needed to enable the feature.
-
01
Require the package
composer require capell-app/login-audit -
02
Register the extension
php artisan capell:extension:enable login-audit -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
3 releases-
v1.0.32Sep 2, 2026 -
v1.0.19Aug 12, 2026 -
v1.0.18Aug 10, 2026
Review evidence for this release
Admin-only access-log surface with no public routes. Sign-in, failure and sign-out events are recorded by hash-aware listeners; the address fingerprint is retained only as a keyed digest and never in clear, the lookup digests are excluded from the privacy export, CSV output is formula-escaped, and the record-detail disclosure carries its own view gate in addition to the resource policy. Two low findings remain open: applying stored settings falls back silently to package defaults when the settings store is unavailable, and the policy permission lookup swallows resolution errors as a denial.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.0.32
- Approval date
- Sep 2, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- Retention purging depends on the vendor scheduled purge command; the last-purged marker is informational and does not itself enforce retention.
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.