env-ci

Get environment variables exposed by CI services

Runssource: GitHubhomepageJavaScriptMITcommit 4df63c629e47

JavaScript, MIT licensed. The project labels itself: appveyor, bamboo, bitbucket, bitrise, buddy, buildkite, ci and circleci.

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

All 113 tests pass under Node 24. Lint passes. Coverage 99.6% statements. The library correctly detects CI services from environment variables.

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
243
forks
47
open issues
13
watchers
5
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 env-ci, 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.

  • System Node v18.19.1 too old for dev dependencies (ava@8, c8@12, etc. require node≥20/≥22). npm install emits EBADENGINE warnings but succeeds with 187 packages.2.5 minutes
  • Tests fail with 'git commit: Author identity unknown' (4 git-helper failures).0.5 minutes
Install time
under a minute
Cold machine to finish
2 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm test (under Node 24) exited 0: lint passed, 113 tests passed, code coverage 99.6% stmts / 95.16% branch
Model tokens used
104,784
Exact commit tested
4df63c629e47
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- **Install**: `npm install` succeeded under Node 18 but emitted 21 EBADENGINE warnings — dev deps …
- **Fix**: Missing git identity caused 4 test failures (git commit in helper could not auto-detect …
- **Verification**: `npm test` exited 0 — lint passed (all files match Prettier style), 113 tests p…
- **Mock usage**: No real CI credentials were needed. Each service test sets its own environment va…
tokens used
104,784
All 113 tests pass, lint passes, coverage 99.6%. Let me compile the final structured report.
**Summary of work done:**
- **Install**: `npm install` succeeded under Node 18 but emitted 21 EBADENGINE warnings — dev deps …
- **Fix**: Missing git identity caused 4 test failures (git commit in helper could not auto-detect …
- **Verification**: `npm test` exited 0 — lint passed (all files match Prettier style), 113 tests p…
- **Mock usage**: No real CI credentials were needed. Each service test sets its own environment va…

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.5 minutes.
  • 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 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.

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

Topics (from GitHub)

appveyorbamboobitbucketbitrisebuddybuildkitecicirclecicirrus-cicodeshipcontinuous-integrationdroneenvironmentgitlabjenkinssemaphoreshippabletravisvstswercker

Embed the badge

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

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

Questions

Does env-ci run?
Yes. env-ci runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test env-ci?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4df63c629e47. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test env-ci?
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 env-ci take to install?
0.5 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 env-ci need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing env-ci?
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 env-ci?
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