bumblebee
Read-only developer endpoint scanner for on-disk package, extension, and developer-tool metadata, built to check exposure to known software supply-chain compromises.
Runssource: GitHubGoApache-2.0commit 8ef7fbce5748
Go, Apache-2.0 licensed. The project labels itself: golang, package inventory and supply chain security.
bumblebee runs. An Argusic agent installed it in 4 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The bumblebee binary builds, runs, passes all 23 test packages, passes selftest with 5 findings in 4ms, and executes a real baseline scan producing valid NDJSON package records.
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.
- Go 1.25+ not present in container1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test ./... exited 0, all 23 packages passed; ./bumblebee selftest printed 'selftest OK (5 findings in 4ms)'; ./bumblebee scan --profile baseline --root /work/repo emitted correct NDJSON with 5 package records and a scan_summary
- Model tokens used
- 58,430
- Exact commit tested
- 8ef7fbce5748
- 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 2, 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.
{"record_type":"scan_summary","record_id":"scan_summary:67beef9be886706dbf15150c2662aa2b9be8a3d9145…
{"record_type":"diagnostic","record_id":"diagnostic:51ad422b87c0c29fc4d533ef6baa8409f4df109d8d8eb3a…
Everything works. Let me verify there are no unresolved issues by checking the GOPATH warning.
exec
/bin/sh -lc 'export PATH="/home/runner/go/bin:$PATH" && export GOROOT=/home/runner/go && export GOP…
succeeded in 0ms:
/home/runner/go
/home/runner/work
All verified. Here's the final report:
tokens used
58,430
All verified. Here's the final report: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 4 minutes, faster than the median of the 8 comparable projects Argusic has measured.
- Recovered from all 1 error 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.
Of the 9 golang projects Argusic has installed and timed, bumblebee was the 5th fastest to reach a running state, and 8 of 9 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 4 minutes after the clone.
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/bumblebee)Questions
- Does bumblebee run?
- Yes. bumblebee runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test bumblebee?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8ef7fbce5748. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test bumblebee?
- 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 bumblebee take to install?
- 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 bumblebee need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing bumblebee?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does bumblebee compare with the alternatives?
- Of the 9 golang projects Argusic has installed and timed, bumblebee was the 5th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for bumblebee?
- 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.