us-congress-comps

Statute Compilations — non-codified law as amended, snapshotted daily because govinfo overwrites it in place and keeps no archive.

Generated by us-congress-pipeline. This repository holds data only: nothing in it is edited by hand, and all of it can be rebuilt from the upstream sources at any time.

Is this still maintained? STATUS.md in the pipeline carries the date the daily job last ran. If that date has stopped moving, so has this.

What is here

• 3 daily snapshots on snapshots, one commit each
• 2,681 compilations as govinfo published them, one file per compilation, so a diff shows what changed
• a main branch holding this README and the license

Built from govinfo COMPS.

Using it

git clone git@github.com:junxit/us-congress-comps.git
cd us-congress-comps
git checkout snapshots

# what changed in the collection on a given day
git show --stat HEAD

# the history of one compilation, across every snapshot
git log --follow -p -- COMPS-10653.xml

# the collection as it stood on a date
git checkout "$(git rev-list -1 --before=2026-08-04 snapshots)"

Each commit is one day's snapshot of the whole collection, and its message records how many compilations changed and how many were withdrawn. snapshot.json at the root carries the date and the package count, so a day on which nothing changed still leaves a commit — the difference between checked, and identical and never checked is the whole point of the repository.

What to watch out for

This is a derived copy, not an official source of United States law. It is generated automatically and published without review. For authoritative text, use uscode.house.gov or govinfo.gov.

This exists because the source does not keep its own history. govinfo replaces a Statute Compilation in place when it is amended and keeps no version archive, so once a compilation is superseded the previous text is gone from the internet. These commits are the only remaining record of what the collection held on the days they were taken.

A gap between commit dates is a gap in the record, not a quiet period. Every snapshot day is committed, including days on which nothing changed, so a missing date means no snapshot was taken and whatever changed that day cannot be recovered from anywhere.

These are compilations, not codified law. A compilation states an act as amended through a given public law — the Social Security Act, for instance — which is a different thing from the US Code's arrangement of the same material. For the codified text see us-congress-code.

The other repositories

This is one of a set. The pipeline that generates them tracks what exists and what is still queued.

Repository	Phase	Holds	State
us-congress-pipeline	0	The ETL itself. Generates every repository below.	the pipeline
us-congress-code	1	The codified US Code. One commit per OLRC release point, tagged, with per-law attribution from Table III.	built
us-congress-bills-{congress}	2	One branch per measure; one commit per bill text version.	12 of these built
us-congress-statutes	5	Statutes at Large — session laws as enacted, volumes 1–137.	built
us-congress-record-{congress}	6	Congressional Record floor proceedings as text, 1994 to present, sharded by Congress and linked to bills by metadata.	17 of these built
us-congress-comps ← you are here	11	Statute Compilations — non-codified law as amended, snapshotted daily because govinfo overwrites it in place and keeps no archive.	built

us-congress-bills-{congress} — 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119

us-congress-record-{congress} — 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119

License

The federal text here is a work of the United States Government and is not subject to copyright under 17 U.S.C. § 105 — it is public domain, and no rights are asserted over it.

The layer this project authored around it — the Markdown conversion, the structure of the history, the commit messages and the prose in files like this one — is © 2026 Jade Naaman, all rights reserved. See LICENSE.