Login Audit
Investigate unusual sign-ins with a clear access history.
- Version
- 1.0.51
- Released
- 20 October 2026
- Licence
- Commercial
Price £19.00
Check access and installationCheck your application before checkout
Use it in your project
Review authentication activity when an account needs attention. Filter the records, inspect suspicious-login alerts and retain the evidence for the period you choose.
Picture it on your site
When a customer reports unexpected account activity, use the authentication records to establish the sequence before taking action. Agree an appropriate retention period and who may review the evidence. A readable access history supports investigation close to the account, but it is not a replacement for the application security controls or an incident process.
6 captures
Manage access and accountability
- Record and export authentication activity.
- Configure suspicious-login alerts and retention.
Is this right for your project?
Decide what is being protected
Write down the protected resource, the people who should reach it and the decision that grants or removes access. That makes the extension part of a clear application policy instead of an isolated setting. Check the supported controls against your actual routes and records. The package does not decide your organisation's policy, and it should not be treated as a substitute for the rest of your security review.
Check refusal as well as access
Test an authorised person, an unauthorised person and a changed or revoked permission. Inspect both the response and the recorded activity where the package supplies it. Your application still owns authentication, role assignment and any routes outside the package's protection boundary. A visible admin control is not enough to establish that every public path is covered.
You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy
Your renewal price stays locked while you renew continuously, including during the grace period. After a full lapse, renewal uses the current list price.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Paid checkout adds access to the purchasing account after payment. Add a free package to your account, then review compatibility and site impact before installing it.
Explore the available extensions on the demo site.
Before you install
Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.
-
01
Require the package
composer require capell-app/login-audit -
02
Install the extension
php artisan capell:extension-install capell-app/login-audit
Release and review evidence
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.51 Oct 20, 2026
- Recent activity
- 19 approved releases in the last 12 months
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.51
- Approval date
- Oct 19, 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.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
10 releases-
v1.0.51Oct 20, 2026 -
v1.0.50Oct 17, 2026 -
v1.0.49Oct 9, 2026 -
v1.0.48Oct 9, 2026 -
v1.0.47Oct 8, 2026 -
v1.0.46Oct 8, 2026 -
v1.0.45Oct 7, 2026 -
v1.0.44Oct 4, 2026 -
v1.0.43Oct 1, 2026 -
v1.0.42Sep 29, 2026
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.