relivator
🏬 relivator: next.js 15 react 19 ecommerce template ▲ better-auth polar shadcn/ui tailwind drizzle orm typescript ts radix, postgres neon, app router saas commerce ecommerce shop pricing payments dark mode full stack free ⭐ more stars 👉 more features
Runs with mockssource: GitHubhomepageTypeScriptMITcommit a1871b006ab0
TypeScript, MIT licensed. The project labels itself: drizzle orm, e commerce, ecommerce, next auth, nextauthjs, nextjs, nextjs boilerplate and nextjs example.
relivator runs, with stand-ins for the services it depends on. An Argusic agent installed it in 6 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
bun install and next build succeed, dev server serves HTTP 200 on /, and all 11 tests (env validation + mocked payment service) pass.
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.
- bun not found in PATH; npm install -g bun failed due to EACCES on /usr/local/lib/node_modules2 minutes
- next build failed with type error: 'User' type missing 'uploads' property in src/lib/queries/uploads.ts1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- bun test ./.tests: 11 pass, 0 fail; bun run build: compiled successfully; bun run dev: curl localhost:3000 returned HTTP 200
- Model tokens used
- 42,764
- Exact commit tested
- a1871b006ab0
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec
/bin/sh -lc 'export PATH="$HOME/.npm-global/bin:$PATH"; cd /work/repo && next version 2>&1; echo "-…
succeeded in 0ms:
/bin/sh: 1: next: not found
1.4.2
v18.19.1
Now I have all the data I need. Let me compile the final report.
`bun run dev` started the server, and `curl -s -o /dev/null -w "%{http_code}" http://localhost:3000…
tokens used
42,764
Now I have all the data I need. Let me compile the final report.
`bun run dev` started the server, and `curl -s -o /dev/null -w "%{http_code}" http://localhost:3000…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 6 minutes.
- Recovered from all 2 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.
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.05 |
Topics (from GitHub)
drizzle-orme-commerceecommercenext-authnextauthjsnextjsnextjs-boilerplatenextjs-examplenextjs-starternextjs-tailwindnextjs-templatenextjs14nextjs15radix-uishadcnshadcn-uistarterstripet3-stacktemplate
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/relivator)Questions
- Does relivator run?
- relivator runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 6 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test relivator?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a1871b006ab0. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test relivator?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does relivator take to install?
- 6 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 relivator need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing relivator?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for relivator?
- 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.