summon

CLI that provides on-demand secrets access for common DevOps tools

Runssource: GitHubhomepageGoMITcommit d42f0517dd7e

Go, MIT licensed. The project labels itself: command line tool, conjbot notify, conjur community team, golang, secret distribution and summon.

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

Summon builds from source and runs: the binary answered --help/--version, all 103 unit tests passed, and it retrieved a secret through the built-in Conjur provider against a local HTTPS mock (authenticate then secret fetch, value printed to the child process), plus the external-provider path returned the fake provider value; mock server was stopped afterward.

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
2
last tested
stars
764
forks
71
open issues
1
watchers
36
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 summon, 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.

  • go: not found in container (no Go toolchain, no Docker for the scripted test path)1 minute
  • mock Conjur server exited after its launching shell ended (connection refused)1 minute
Install time
3 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go test -count=1 ./... -> all 8 packages ok, 103 tests passed; /tmp/summon --provider conjur --yaml 'MY_SECRET: !var env/creds/db/password' -- printenv MY_SECRET -> printed mock-secret-value-42, exit 0; /tmp/summon --help and --version -> printed usage and 'summon version unset-unset'
Model tokens used
271,256
Exact commit tested
d42f0517dd7e
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.

- Built-in Conjur provider against a schema-correct HTTPS mock I stood up (Go `httptest`-style serv…
- Uninvadable README claims (docs site, GitHub releases) were not exercised; recorded as not checke…
**Errors encountered**
- `go: not found` (and `docker: not found` for the scripted Docker paths) — fixed by using the proj…
- Mock server initially died after the shell session ended (connection refused) — fixed by relaunch…
- Minor pre-existing cosmetic gap: built binary reports `version unset-unset` because `VERSION` is …
**Result**
`install_succeeded`: true — `go build ./cmd` and `go build ./...` both exited 0.
`launch_succeeded`: true — binary `--help`/`--version` ran; full unit suite executed.
`test_depth`: `tier1_real` — real binary and library exercised against a standing HTTPS mock.
```
```

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 3 minutes, faster than the median of the 12 comparable projects Argusic has measured.
  • 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.
  • Measured 2 times, so the result is not a one-off.

Of the 13 command-line-tool projects Argusic has installed and timed, summon was the 6th fastest to reach a running state, and 12 of 13 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 3 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.03
Argusic Runner1/3Runs100.000.06

Topics (from GitHub)

command-line-toolconjbot-notifyconjur-community-teamgolangsecret-distributionsummon

Embed the badge

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

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

Questions

Does summon run?
Yes. summon runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test summon?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d42f0517dd7e. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test summon?
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 summon take to install?
3 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 summon need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing summon?
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 summon compare with the alternatives?
Of the 13 command-line-tool projects Argusic has installed and timed, summon was the 6th fastest to reach a running state, and 12 of 13 reached one at all.
Where is the evidence for summon?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion