katana
A next-generation crawling and spidering framework.
Runssource: GitHubGoMITcommit 09c83e9a8b12
Go, MIT licensed. The project labels itself: cli, crawler, gocrawler, hacktoberfest, headless, spider framework and web spider.
katana runs. An Argusic agent installed it in 8 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Katana v1.7.0 builds and runs: go test ./... passes all unit tests, the 5 functional tests (standard crawl, depth 3, headless, two authenticated recorded-flow variants) all pass, and the binary crawls a live HTTP target discovering URLs.
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
- 8 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test ./... exited 0, all tests passed (no failures); functional-test binary -dev ./katana exited 0, all 5 tests passed (Standard Mode Crawl, Standard Mode Depth 3, Headless Browser Crawl, Recorded Flow Authenticated Crawl, Recorded Flow Explicit Steps Crawl); ./katana -version returned v1.7.0; ./katana -u http://127.0.0.1:9999 -d 1 -silent successfully crawled a local HTTP server and returned discovered endpoints
- Model tokens used
- 195,253
- Exact commit tested
- 09c83e9a8b12
- 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.
/bin/sh -lc 'echo "Session started around 10:15, current:" ; date +%s' in /work/repo succeeded in 0ms: Session started around 10:15, current: 1790504601 exec /bin/sh -lc 'echo "Started at 1790504100 (10:15 UTC), ended at 1790504601, delta = $(( (1790504601 … succeeded in 0ms: Started at 1790504100 (10:15 UTC), ended at 1790504601, delta = 8 minutes All systems went flawlessly. No errors to fix, and I verified the binary against both a real HTTP t… tokens used 195,253 All systems went flawlessly. No errors to fix, and I verified the binary against both a real HTTP t…
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.
- 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.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 25 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 26 cli projects Argusic has installed and timed, katana was the 21st fastest to reach a running state, and 24 of 26 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 8 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Run history
Topics (from GitHub)
clicrawlergocrawlerhacktoberfestheadlessspider-frameworkweb-spider
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/katana)Questions
- Does katana run?
- Yes. katana runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test katana?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 09c83e9a8b12. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test katana?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does katana take to install?
- 8 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 katana need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing katana?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does katana compare with the alternatives?
- Of the 26 cli projects Argusic has installed and timed, katana was the 21st fastest to reach a running state, and 24 of 26 reached one at all.
- Where is the evidence for katana?
- 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.