Cockroach Crawler 0.7.0
Cockroach Crawler 0.7.0 promotes the reviewed 0.7 package and API surface from release candidate to stable availability. This is a stable-package decision, not a benchmark-leadership or universal-quality claim.
Published benchmark
The opt-in Node quality balanced path records the following source-pinned result on 511 previously observed WCEB v1.0 pages:
| Pages | Precision | Recall | Macro F1 | Required-snippet recall | Unwanted inclusion |
|---|---|---|---|---|---|
| 511 | 0.894101 | 0.926022 | 0.890524 | 0.864090 | 0.111383 |
This is explicitly observed-development evidence. The project previously inspected and iterated against the upstream partition, so it is not untouched held-out confirmation, a rounded universal 0.90 result, or a claim of superiority over another crawler. Browser automation quality, OCR, public-network throughput, and universal extraction quality are outside this benchmark.
The stable package preserves the reviewed 0.7.0-rc.1 runtime, dependency lock, public evidence, paper, and Zenodo files byte-for-byte except for approved stable release/version metadata. The attached JSON files expose the observed, full-development, fail-closed, and same-scorer comparison evidence directly.
Provenance
- Stable source commit:
b80984625256821484731f29aca4d65011507628 - Benchmark-generation source:
90825063d447f07345388d040b1428a311109c2b - Reviewed RC package commit:
62f270636a019c9bcc617a13fe254640bcd06925 - WCEB revision:
62ff86d12ea72c80c31fb810ff1a724fad687bea - Trusted npm workflow: run 31325647731
- npm package:
cockroach-crawler@0.7.0 - Registry attestation:
cockroach-crawler@0.7.0 - npm integrity:
sha512-F5Q4uycSk//Svkong72NlKGKrHx4eAgZE88WO2gupES5Cl1Y50Vlbdi6/8quEJir3UahI3aZRTajF7jZMD0uiA== - npm shasum:
8b7f2c7a7cd3a19768137e9a1629d614638c19a9 - Benchmark JSON SHA-256:
a71c884e9521d1cd1c6326dc07c1d1a5c36344244c45d4900a078ae92a8de535
The npm artifact was published through GitHub Actions trusted publishing with SLSA v1 provenance and a registry signature. A fresh consumer installation verified all 28 export subpaths, all eight CLI bins, package signatures, attestations, and a zero-vulnerability production audit.
Operating boundaries
This release remains fail-closed around public-network admission, DNS and redirect policy, robots enforcement, origin allowlists, resource ceilings, provider authority, and challenge handling. It does not extract hidden cookies, bypass CAPTCHAs or access controls, provide a hosted arbitrary-origin proxy fleet or distributed jobs, claim operating-system sandboxing, make a universal provider claim, or claim complete compatibility with general browser-automation frameworks.