life-kline

🌟 人生K线 - 基于 AI 大模型 + 传统八字命理的人生运势可视化工具。将命运绘制成 K 线图,像看股票一样看人生!支持自托管部署。

Runssource: GitHubhomepageTypeScriptApache-2.0commit 7abf184df370

TypeScript, Apache-2.0 licensed. The project labels itself: ai, bazi, chinese astrology, fortune telling, k line, nodejs, openai and react.

life-kline runs. An Argusic agent installed it in 7 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Server starts on port 3000, health endpoint returns 200, user registration and login work, profile CRUD works, local fortune calculation (daily/monthly/yearly) returns computed results, knowledge articles and cases are served, frontend builds cleanly, and the bazi calculator produces realistic 100-year K-line data.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
484
forks
134
open issues
4
watchers
1
size
2 MB
created
last push

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.

Time lost to each failure while testing life-kline, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • createUserProfile in database.js: 16 SQL placeholders for 15 columns2 minutes
  • npm install failed with ERESOLVE peer dependency conflict on react-helmet-async with React 191 minute
Install time
7 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
curl http://localhost:3000/api/health returned 200 '{"ok":true}'; curl POST /api/auth/register returned 201 with user object; curl POST /api/auth/login returned 200 with JWT cookie; curl POST /api/profiles returned 201 with profile object; curl POST /api/fortune/daily returned 200 with fortune data; curl /api/fortune/monthly/2026/10 returned 200 with monthly fortune; curl /api/fortune/yearly/2026 returned 200 with yearly fortune; curl /api/public/pricing returned 200 with 4 features and 3 packages; curl /api/content/knowledge returned 200 with 5 articles; curl /api/content/cases returned 200 with 3 cases; npx vite build exited 0 producing 30 chunks in 7.89s; node baziCalculator.js produced 100-entry timeline and 100-entry K-line
Model tokens used
490,494
Exact commit tested
7abf184df370
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.

/bin/sh -lc 'pkill -f "node server/index.js" 2>/dev/null; echo "done"' in /work/repo
 exited 143 in 0ms:
Now I have all the data needed. Let me compile the final report.
exec
/bin/sh -lc '# Quick sanity check on total elapsed time
echo "Started at: 17:36"
echo "Current time: $(date +%H:%M)"' in /work/repo
 succeeded in 0ms:
Started at: 17:36
Current time: 17:43
tokens used
490,494

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.
  • Recovered from all 2 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 Apache-2.0, as reported by its host.

What did not, or is not known

  • Took 7 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 237 ai projects Argusic has installed and timed, life-kline was the 145th fastest to reach a running state, and 168 of 237 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 7 minutes after the clone.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.06

Topics (from GitHub)

aibazichinese-astrologyfortune-tellingk-linenodejsopenaireactself-hostedvisualization

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/life-kline.svg)](https://argusic.com/subject/life-kline)

Questions

Does life-kline run?
Yes. life-kline runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test life-kline?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7abf184df370. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test life-kline?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does life-kline take to install?
7 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 life-kline need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing life-kline?
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.
How does life-kline compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, life-kline was the 145th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for life-kline?
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.

Discussion