ovine

ovine由于存在设计缺陷不再更新。 新版会在 ovine-next 重写。 https://github.com/ovineio/ovine-next

Runssource: GitHubhomepageJavaScriptApache-2.0commit cb2d4f989465

JavaScript, Apache-2.0 licensed. The project labels itself: admin, admin template, amis, amis demo, antd, antd design, json and json form.

ovine runs. 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.

Dependencies installed, test suite passes (36/36 tests, 6 suites), CLI binary produces help output, core packages compile with tsc

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.07 (measured)
recorded runs
1
last tested
stars
746
forks
123
open issues
30
watchers
31
size
23 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 ovine, 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.

  • yarn.lock had 2 packages pinned to unreachable Chinese mirror registry.nlark.com3 minutes
  • ttypescript/ttsc has a compatibility crash with Node.js 18 (extends/getter issue)2 minutes
  • CLI binary failed to start because tsc didn't copy webpack plugin .js files to lib/1 minute
Install time
10 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npx jest exited 0 with 6 suites passed and 36 tests passed; node packages/cli/bin/index.js --help printed command usage
Model tokens used
46,275
Exact commit tested
cb2d4f989465
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.

v10.9.2
The test suite already verified the code works. Let me work out the final report. Here's a summary …
All tests passed, and the CLI binary works. Let me compile the final report.
exec
/bin/sh -lc 'date +%s' in /work/repo
 succeeded in 0ms:
1791977717
Let me compile the final report. Here's the summary of everything I did.
2026-10-14T11:35:39.074158Z ERROR codex_core::session: failed to record rollout items: thread 01a13…
tokens used
46,275
Let me compile the final report. Here's the summary of everything I did.

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 10 minutes, faster than the median of the 9 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.
  • 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

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 10 admin projects Argusic has installed and timed, ovine was the 4th fastest to reach a running state, and 8 of 10 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 10 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.07

Topics (from GitHub)

adminadmin-templateamisamis-demoantdantd-designjsonjson-formlow-codeovinereactreact-adminwebpack

Embed the badge

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

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

Questions

Does ovine run?
Yes. ovine runs. 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 ovine?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit cb2d4f989465. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ovine?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ovine 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 ovine need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ovine?
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 ovine compare with the alternatives?
Of the 10 admin projects Argusic has installed and timed, ovine was the 4th fastest to reach a running state, and 8 of 10 reached one at all.
Where is the evidence for ovine?
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