pingap
A reverse proxy like nginx, built on pingora, simple and efficient.
Runssource: GitHubhomepageRustApache-2.0commit 71c4aa98aade
Rust, Apache-2.0 licensed. The project labels itself: pingora and reverse proxy.
pingap runs. An Argusic agent installed it in 27 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 416 tests pass, release binary builds (28MB), and --version reports pingap 0.14.3 with openssl TLS backend; web admin assets (dist/) are built and RustEmbedded.
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.
- etc not running, test_etcd_config_manger fails3 minutes
- Node 18 too old for Vite 8, web admin build fails2 minutes
- test_cert in pingap-certificate uses hardcoded expired certificate2 minutes
- etc background process dies when shell exits2 minutes
- Rust toolchain not installed1 minute
- protoc not found, etcd-client build fails1 minute
- Install time
- 27 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- cargo test --workspace --features=full -- all tests passed (416 total across all crate binaries), release build produces 28MB binary, --version reports 'pingap 0.14.3 (71c4aa98... tls=openssl)'
- Model tokens used
- 95,739
- Exact commit tested
- 71c4aa98aade
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
4. protoc permission denied - chmod +x
5. Web assets build fails (node 18 too old for vite 8) - downloaded node 22 and rebuilt
6. `test_cert` test fails with expired cert - replaced with programmatic cert generation
7. Etcd connection test failure - started etcd
8. port 2379 not accessible initially - had to restart etcd properly with PTY
Let me record the final state:
exec
/bin/sh -lc 'cd /work/repo && export PATH="/tmp/protoc/bin:$HOME/.cargo/bin:$PATH" && cargo build -…
succeeded in 830ms:
Finished `release` profile [optimized] target(s) in 0.93s
tokens used
95,739Replay 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 27 minutes.
- Recovered from all 6 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.
- Measured 2 times, so the result is not a one-off.
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/pingap)Questions
- Does pingap run?
- Yes. pingap runs. Argusic installed and launched it on a clean machine in 27 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test pingap?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 71c4aa98aade. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test pingap?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pingap take to install?
- 27 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 pingap need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pingap?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for pingap?
- 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.