laravel-top
🚀 Real-time monitoring from the command line for Laravel applications.
Runs with mockssource: GitHubPHPMITcommit 1f2ba3c23ced
PHP, MIT licensed. The project labels itself: apm, cli, command line tool, laravel package, metrics and realtime monitoring.
laravel-top runs, with stand-ins for the services it depends on. An Argusic agent installed it in 10 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The laravel-top package installs with Composer under PHP 8.4.23 and its own test suite passes (19 tests, 33 assertions); phpstan and pint report 13 pre-existing style/analysis issues each and the PHPStan turbo accelerator warning shows the static build cannot load dynamic extensions.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Could not stand up a real Redis server: no redis-server binary and system packages cannot be installed; an in-process stream-based fake Redis proved unreliable because the phpredis extension in the static build does not flush buffered requests while the server is in a blocking fgets() (only a raw-socket PING worked end-to-end)31 minutes
- composer test script fails: phpstan analyse reports 13 errors (8 GuiBuilder nullsafe.neverNull, 1 Redis::pipeline() arguments.count, 4 unmatched ignore directives) and pint --test fails on 13 files (single_line_empty_body, new_with_parentheses)8 minutes
- No PHP or Composer installed in the container (no root to apt install); required PHP 8.2+, ext-pcntl, and a Laravel app were absent3 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- php -d memory_limit=-1 vendor/bin/pest --colors=never exited 0: Tests: 19 passed (33 assertions); php -d memory_limit=-1 vendor/bin/phpstan analyse --no-progress exited 0 despite 'Found 13 errors'; php -d memory_limit=-1 vendor/bin/pint --test exited 0 with result:fail on 13 files; php -r (new Redis)->connect('127.0.0.1',6351)->ping() returned true against a TCP RESP mock, confirming TCP sockets work in the static build
- Model tokens used
- 1,931,910
- Exact commit tested
- 1f2ba3c23ced
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
total 64916 drwxrwxr-x 3 runner runner 124 Oct 17 16:17 . drwxr-x--- 8 runner runner 185 Oct 17 16:21 .. drwxrwxr-x 4 runner runner 64 Oct 17 16:17 .composer-cache -rwxr-xr-x 1 runner runner 3642137 Oct 17 16:17 composer -rw-rw-r-- 1 runner runner 59524 Oct 17 16:17 composer-setup.php -rwxr-xr-x 1 runner runner 31737684 Jul 7 05:34 php -rw-rw-r-- 1 runner runner 31024351 Oct 17 16:17 php.tar.gz All work is complete. Here is the final report: tokens used 1,931,910 All work is complete. Here is the final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 10 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 apm projects Argusic has installed and timed, laravel-top was the 2nd fastest to reach a running state, and 4 of 5 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.39 |
Topics (from GitHub)
apmclicommand-line-toollaravel-packagemetricsrealtime-monitoring
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/laravel-top)Questions
- Does laravel-top run?
- laravel-top runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 10 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test laravel-top?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1f2ba3c23ced. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test laravel-top?
- The run that produced this verdict cost $0.39: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does laravel-top take to install?
- 10 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does laravel-top need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing laravel-top?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does laravel-top compare with the alternatives?
- Of the 5 apm projects Argusic has installed and timed, laravel-top was the 2nd fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for laravel-top?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.