invobook
Self-hosted app for Time Tracking, Invoice Generation, Project & Client Management, built with Laravel & Filament.
Runssource: GitHubPHPMITcommit e5f666cef635
PHP, MIT licensed. The project labels itself: client management, filament, filamentadmin, invoice, laravel, php, project management and tailwindcss.
invobook runs. An Argusic agent installed it in 35 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PHP 8.3.6 and Composer 2.11 installed, all 169 composer packages installed, SQLite database configured with 19 migrations run, artisan CLI works, dev server serves HTTP 200 on / and /login, unit test passes
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 100 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.
- Required PHP extensions (dom, intl, tokenizer, fileinfo, xmlreader, xmlwriter, simplexml, zip) missing8 minutes
- PHP 8.x not installed in container5 minutes
- PDO SQLite driver not registering - undefined symbols5 minutes
- MySQL not available but project defaults to MySQL5 minutes
- libzip shared library missing for zip extension3 minutes
- Composer not installed2 minutes
- Install time
- 35 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- php --version returns 'PHP 8.3.6 (cli)'; php artisan --version returns 'Laravel Framework 11.31.0'; php vendor/bin/pest tests/Unit/ExampleTest.php exits 0 with 1 passed; php artisan migrate:status shows 19 migrations ran; php artisan serve starts dev server on 8087; curl / returns HTTP 200; curl /login returns HTTP 200
- Model tokens used
- 158,915
- Exact commit tested
- e5f666cef635
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
echo "---" echo "Total packages: $(ls -d vendor/*/ 2>/dev/null | wc -l)"' in /work/repo succeeded in 130ms: Install steps took approximately 35 minutes 2023_05_23_102943_create_rates_table ............................... [1] Ran 2023_05_30_154444_create_team_invitations_table .................... [1] Ran 2023_05_31_152208_create_invoices_table ............................ [1] Ran 2023_05_31_165713_create_invoice_items_table ....................... [1] Ran -rw-rw-r-- 1 runner runner 172032 Oct 4 01:39 /work/repo/storage/app.sqlite Total packages: 62 tokens used 158,915
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
- Reached a running state on a clean machine, with the session recorded.
- Installed in 35 minutes.
- Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
Topics (from GitHub)
client-managementfilamentfilamentadmininvoicelaravelphpproject-managementtailwindcsstime-tracker
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/invobook)Questions
- Does invobook run?
- Yes. invobook runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test invobook?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e5f666cef635. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test invobook?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does invobook take to install?
- 35 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 invobook need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing invobook?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for invobook?
- 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.