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 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
bumblebee v0.0.0-20260923154808 runs as a static Go binary on Linux amd64; the built-in selftest passes, the full test suite (23 modules) passes, and a baseline scan against the local environment completes successfully discovering 1061 package records across 2 ecosystems (go, pypi) from 22624 files considered.
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
- 3 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- Built: 'go build -o bumblebee ./cmd/bumblebee' produced the binary. Test suite: 'go test ./...' exited 0 with 23/23 modules OK. Selftest: '/work/repo/bumblebee selftest' printed 'selftest OK (5 findings in 2ms)'. Baseline scan: '/work/repo/bumblebee scan --profile baseline' exited 0, scanned 22624 files, emitted 1061 package records across go/pypi ecosystems, summary status 'complete'. Binary version: '/work/repo/bumblebee version' printed its version, commit, build time, and Go runtime.
- Model tokens used
- 46,812
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
cd /work/repo && git log --oneline -1 2>&1; echo "---"; cat /work/repo/VERSION' in /work/repo succeeded in 0ms: --- TIMING --- Thu Oct 1 07:19:26 UTC 2026 Started: -rw-r--r-- 1 runner runner 6 2026-10-01 07:16:01.377434903 +0000 /work/repo/VERSION 8ef7fbc Merge pull request #80 from ronheichman/advisory-catalog/memtensor-2026-09-23 0.1.1 All systems are green. Here's the final report. tokens used 46,812 All systems are green. 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 3 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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.
- Following its own README: the documented path worked with nothing to fix.
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 3 minutes, hitting 0 errors 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. One attempt is 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.02: 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?
- 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 bumblebee need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing bumblebee?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for bumblebee?
- 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.