sponge
A powerful and easy-to-use Go development framework that enables you to effortlessly build stable, reliable, and high-performance backend services with a "low-code" approach.
Runssource: GitHubhomepageGoMITcommit beef9eecdc5e
Go, MIT licensed. The project labels itself: ai assistant, ai generated code, cloud native, code generation, custom templates, developer tools, development framework and gin.
sponge runs. An Argusic agent installed it in 20.4 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The sponge CLI v1.16.1 is installed with all 12 dependency plugins, the project builds from source with go build ./... 79 test packages pass, and the code generation UI server runs on port 24638 serving the web interface and RESTful APIs including listing database drivers and LLM options.
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.
- Install time
- 20 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test ./pkg/... passed 67/67 test packages; go test ./internal/... passed 12/12 test packages; curl http://127.0.0.1:24638/api/v1/listDrivers returned 200 with valid JSON listing 5 DB drivers; curl http://127.0.0.1:24638/api/v1/listLLM returned 200 with LLM options; sponge -v returned v1.16.1
- Model tokens used
- 45,448
- Exact commit tested
- beef9eecdc5e
- 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.
Start: 1794327360
Now: 1794328587
exec
/bin/sh -lc 'echo "scale=2; (1794328587 - 1794327360) / 60" | bc' in /work/repo
exited 127 in 0ms:
/bin/sh: 1: bc: not found
exec
/bin/sh -lc "python3 -c \"print(f'{(1794328587 - 1794327360)/60:.1f}')\"" in /work/repo
succeeded in 0ms:
20.4
tokens used
45,448Replay 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.
- 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 20.4 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
Of the 12 ai-assistant projects Argusic has installed and timed, sponge was the 7th fastest to reach a running state, and 9 of 12 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.
- 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
Topics (from GitHub)
ai-assistantai-generated-codecloud-nativecode-generationcustom-templatesdeveloper-toolsdevelopment-frameworkgingo-spongegrpcgrpc-gatewaylow-codemicroserviceprotobufrestful-apispongeweb
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sponge)Questions
- Does sponge run?
- Yes. sponge runs. Argusic installed and launched it on a clean machine in 20 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test sponge?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit beef9eecdc5e. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test sponge?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sponge take to install?
- 20.4 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 sponge need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sponge?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does sponge compare with the alternatives?
- Of the 12 ai-assistant projects Argusic has installed and timed, sponge was the 7th fastest to reach a running state, and 9 of 12 reached one at all.
- Where is the evidence for sponge?
- 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.