cifuse

Turn noisy CI logs into grouped failures, exact evidence and investigation steps. Offline CLI, reusable GitHub Action and bilingual browser workbench. No API keys.

Runssource: GitHubJavaScriptMITcommit 6a38b949f260

JavaScript, MIT licensed. The project labels itself: automation, ci, cli, continuous integration, debugging, developer tools, devops and github actions.

cifuse runs. An Argusic agent installed it in 0 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

All 42 tests pass, CLI produces valid analysis reports in markdown and JSON format, and the static site builds to dist/ with no errors.

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.01 (measured)
recorded runs
1
last tested
stars
203
forks
0
open issues
0
watchers
0
created
-
last push
-

Subject data from GitHub, linked at the top of this page. 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.

Install time
under a minute
Cold machine to finish
under a minute
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
npm test exited 0, 42 passed; node bin/cifuse.js --demo printed structured analysis; node bin/cifuse.js --format json output valid JSON schema; npm run build produced dist/
Model tokens used
23,200
Exact commit tested
6a38b949f260
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.

    "signals": 8,
    "groups": 5,
    "new": null,
    "resolved": null
  },
  "findings": [
    {
      "signature": "type-error:src/api.ts(#,#): error ts2322: type 'string' is not assignable to ty…
All verified. Here's the final report:
tokens used
23,200
All verified. Here's the final report:

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 0 minutes, faster than the median of the 38 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • 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.

Of the 39 automation projects Argusic has installed and timed, cifuse was the 1st fastest to reach a running state, and 27 of 39 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 0 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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.01

Topics (from GitHub)

automationciclicontinuous-integrationdebuggingdeveloper-toolsdevopsgithub-actionsgithub-pagesjavascriptlog-analysisnodejsoffline

Embed the badge

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

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

Questions

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