ghs

GitHub Search: Platform used to crawl, store and present projects from GitHub, as well as any statistics related to them

Runs with mockssource: GitHubhomepageJavaMITcommit 9f108a5799e7

Java, MIT licensed. The project labels itself: bootstrap, crawler, csv export, dataset generation, docker compose, git, github and java 17.

ghs runs, with stand-ins for the services it depends on. An Argusic agent installed it in 13 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Java/Maven project compiles, packages, and passes all 14 unit tests. The Spring Boot server starts on port 8080 with H2 database, serves health/info/actuator endpoints at 200, exposes the OpenAPI/Swagger API spec, and the frontend builds to dist/.

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

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.24 (measured)
recorded runs
1
last tested
stars
204
forks
25
open issues
33
watchers
0
size
42 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 ghs, 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.

  • MySQL database required but not available7 minutes
  • Java and Maven not in container3 minutes
Install time
13 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
mvn test: 14 passed, 0 failed. curl localhost:8080/api/actuator/health returned 200 with {"status":"UP","groups":["details"]}. curl localhost:8080/api/ returned 200 with Spring Boot response headers. curl localhost:8080/api/openapi returned OpenAPI 3.0 spec with title 'GitHub Search' and paths /, /version, /r/{owner}/{repo}, /r/{id}, /r/topics. npm run build produced dist/ with minified index.html, css, js, and icons.
Model tokens used
717,682
Exact commit tested
9f108a5799e7
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

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

Let me also clean up the temporary files.
exec
/bin/sh -lc '# Get elapsed time
echo "Install time: ~13 minutes total"' in /work/repo
 succeeded in 0ms:
Install time: ~13 minutes total
Here is the complete report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 13, "e…
tokens used
717,682
Here is the complete report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 13, "e…

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

  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 13 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 4 bootstrap projects Argusic has installed and timed, ghs was the 3rd fastest to reach a running state, and 3 of 4 reached one at all.

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/3Runs with mocks92.000.24

Topics (from GitHub)

bootstrapcrawlercsv-exportdataset-generationdocker-composegitgithubjava-17json-exportmining-software-repositoriesmsrmysqlplatformrepositorysearch-enginespring-bootspring-boot-applicationspring-boot-serversql-dumpxml-export

Embed the badge

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

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

Questions

Does ghs run?
ghs runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 13 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test ghs?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9f108a5799e7. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ghs?
The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ghs take to install?
13 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 ghs need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ghs?
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 ghs compare with the alternatives?
Of the 4 bootstrap projects Argusic has installed and timed, ghs was the 3rd fastest to reach a running state, and 3 of 4 reached one at all.
Where is the evidence for ghs?
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