colorls
A Ruby gem that beautifies the terminal's ls command, with color and font-awesome icons. :tada:
Runssource: GitHubRubyMITcommit ec2fbcd36f6b
Ruby, MIT licensed. The project labels itself: cli, color, eye candy, gem, icons, ls, ruby and terminal.
colorls runs. An Argusic agent installed it in 18 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
colorls gem 1.5.0 installed from source, all 40 integration tests and 90/91 RSpec tests pass, binary lists directory contents with colorized icons.
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
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.
- Ruby not installed in environment6 minutes
- psych (YAML) Ruby extension failed to build (missing libyaml)3 minutes
- zlib Ruby extension failed to build (missing headers)2 minutes
- Bundler dependency resolution failed on version constraints2 minutes
- Install time
- 18 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- colorls -1 listed files with icons; 40/40 integration tests passed; rspec 90/91 passed (1 pre-existing regex issue)
- Model tokens used
- 113,052
- Exact commit tested
- ec2fbcd36f6b
- 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.
**Elapsed:** ~18 minutes Here's the summary: **Errors encountered and fixed:** 1. **Ruby not installed** — Built Ruby 3.3.12 from source via rbenv/ruby-build (~6 min, compiles fr… 2. **zlib extension not compiled** — Extracted `zlib.h` from `zlib1g-dev` .deb, built and installed… 3. **psych extension (YAML) not compiled** — Built `libyaml` 0.2.5 from source with cmake, then bui… 4. **Bundler dependency conflicts** — Directly installed correct pinned versions of `rdoc`, `ruboco… **Verified how:** - `colorls --version` → prints `1.5.0` - `colorls -1` → lists repository files with icons successfully - `bash test/run` → **40/40 integration tests passed** - `rspec` → **90/91 examples passed** (1 pre-existing regex-pattern-test issue with `\n` escaping, …
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 4 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.
What did not, or is not known
- Took 18 minutes to install, slower than the median of the 41 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 42 cli projects Argusic has installed and timed, colorls was the 40th fastest to reach a running state, and 38 of 42 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.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/colorls)Questions
- Does colorls run?
- Yes. colorls runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test colorls?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ec2fbcd36f6b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test colorls?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does colorls take to install?
- 18 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 colorls need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing colorls?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does colorls compare with the alternatives?
- Of the 42 cli projects Argusic has installed and timed, colorls was the 40th fastest to reach a running state, and 38 of 42 reached one at all.
- Where is the evidence for colorls?
- 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.