From the forge's lake.
build time
seconds per build of the pagestable
pushes
pushes a daytable
time to land
hours from a review's first push to landing, by when it landedtable
revisions per review
reviews by how many revisions they were pushed intable
ci results
attestations a day, passed and failedtable
ci duration
seconds per run of .forge/citable
| repository | pushes | builds | median build | landed | ci passed | last push |
|---|
datathe rows behind the charts, for public repos only, as Parquet
| insights.json | what the charts draw |
| events.parquet | pushes, comments, approvals and builds as they happened |
| builds.parquet | each page build: time spent, pages written |
| reviews.parquet | each review's lifecycle: created, revisions, approvals, landed or closed |
| ci.parquet | each CI attestation: commit, tree, result, duration, system, signer |
| ci_metrics.parquet | each metric an attestation reported: name, value, unit, with its commit and result |
DuckDB reads them over HTTP in byte ranges, so a query fetches only what it needs:
duckdb -c "SELECT result, count(*), median(duration_s) FROM 'https://src.rest/insights/ci.parquet' GROUP BY result"