Skip to main content

Interfaces & Data

This is the material a README typically leaves implicit: what CloneCratesio actually talks to, what it emits, and where it sits in the wider Aptlantis toolchain.

Interfaces

InterfaceType
download-cratesCLI (Go)
generate-sidecarsCLI (Go)
extract-bundlesCLI (Go)
Clone-Index.pyWrapper script (Python)
/metricsHTTP — Prometheus
/api/statusHTTP — JSON status
/debug/pprof/HTTP — pprof profiling

Produces

  • .crate files (loose-file mirror)
  • Rolling .tar.zst bundle archives
  • manifest.jsonl — per-run JSONL audit log (path, size, sha256, yanked, timestamp)
  • Per-crate .crate.json sidecars, or aggregated JSONL sidecar streams
  • bundles.index.jsonl and per-bundle manifests
  • Prometheus metrics on /metrics
  • pprof endpoints and /api/status JSON

Consumes

  • A local crates.io-index git checkout
  • Optional checksums JSONL input
  • Newline-delimited URL lists
  • Bundles (for extract-bundles)
  • Operator-provided flags and filesystem paths

Depends on

  • Go toolchain (1.25+ documented)
  • Python 3.9+ (for the wrapper)
  • git (for index clone/update)
  • klauspost/compress/zstd (Go library)
  • prometheus/client_golang
  • OS filesystem with sufficient disk I/O

Used by

  • Single-operator mirror runs
  • Airgap transport and offline verification workflows
  • Local ecosystem analysis and dataset generation
  • Internal dashboards scraping the Prometheus endpoint
  • Downstream forensic/metadata tooling

Where it sits in Aptlantis governance

CloneCratesio's primary standard is CTS (Command Tool Standard), with WGS and PPS as additional standards it inherits from. Its manifest chains up through CTS.manifest.toml. It's flagged active-core lifecycle, meaning it's considered a load-bearing tool in the portfolio even while paused.

The biggest gap between CloneCratesio's current state and full CTS compliance is documentation of command contracts, not functionality — see the Roadmap page. The manifest's own known_gaps note: "Current build, test, artifact, and release posture were not executed during the governance migration."