Password-Manager
Self-hosted Password Manager based on Laravel 10 + PHP 8 + MySQL 8. Gestor de Contraseñas basado en Laravel 10 + PHP 8 + MySQL 8.
Runssource: GitHubPHPMITcommit ba8268a6f0cc
PHP, MIT licensed. The project labels itself: laravel, password manager and php.
Password-Manager runs. An Argusic agent installed it in 12 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Laravel 10 Password Manager app is fully installed and functional: composer dependencies resolved, APP_KEY generated, storage symlink fixed, icon search adapted to use Google favicons API, and all 316 PHPUnit tests pass with 1417 assertions.
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 60 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.
- Composer platform conflict: vimeo/psalm requires PHP <= 8.35 minutes
- No PHP binary in container3 minutes
- Google Image Search scraping broken (regex no longer matches Google page)2 minutes
- SESSION_COOKIE env var missing causing TypeError in StartSession middleware1 minute
- public/storage was a directory instead of symlink1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- cd /work/repo && /tmp/php-bin vendor/bin/phpunit --no-coverage exited 0, 316 tests passed with 1417 assertions
- Model tokens used
- 443,166
- Exact commit tested
- ba8268a6f0cc
- 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.
**Errors found and fixed:**
1. **No PHP binary** — Fixed by downloading FrankenPHP 8.4.2 (static binary with many extensions)
2. **Composer platform conflict** (vimeo/psalm 5.x requires PHP ≤8.3) — Fixed with `--ignore-platfo…
3. **SESSION_COOKIE null in .env** causing Symfony `InputBag::get()` TypeError — Fixed by adding `S…
4. **public/storage was a regular directory** instead of symlink, causing icon path test failure — …
5. **Google Image Search scraping broken** (Google now serves JS-rendered pages) — Fixed `app/Servi…
**Verification:** All 316 tests pass with 1417 assertions
exec
/bin/sh -lc "echo \"ARGUSIC_RESULT:{\\\"install_succeeded\\\":true,\\\"launch_succeeded\\\":true,\\…
succeeded in 0ms:
tokens used
443,166Replay 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 12 minutes.
- Recovered from all 5 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.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.12 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.12 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/password-manager)Questions
- Does Password-Manager run?
- Yes. Password-Manager runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test Password-Manager?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ba8268a6f0cc. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Password-Manager?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Password-Manager take to install?
- 12 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 Password-Manager need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Password-Manager?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Password-Manager?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.