Data Freshness & Sources
PublicLaws.org is only useful if readers can trust the information. Our evergreen pipeline re-downloads every dataset from its official government source on a schedule, hashes the parsed output, and rebuilds the site only when the law actually changed. The table below is generated directly from that pipeline's latest run.
Dataset Status
| Dataset | Records | Last verified | Last changed | Links |
|---|---|---|---|---|
| U.S. Code | 0 | 2026-08-23 | 2026-08-23 | Official source · method |
| CFR titles (metadata) | 408 | 2026-08-23 | 2026-08-23 | Official source · method |
| Code of Virginia | 33,702 | 2026-08-23 | 2026-08-23 | Official source · method |
| D.C. Code | 21,112 | 2026-08-23 | 2026-08-23 | Official source · method |
| Delaware Code | 8,882 | 2026-08-23 | 2026-08-23 | Official source · method |
| Oregon Revised Statutes | 33,299 | 2026-08-23 | 2026-08-23 | Official source · method |
How We Keep Data Current
For each jurisdiction we ingest only from official government publications: bulk CSV/XML where offered (e.g., Virginia's Legislative Information System, the D.C. Council's official XML repository), or the government's own published code pages. Every statute page links back to the authoritative section on the government site so you can verify the current text yourself.
The refresh workflow checks each source, computes a SHA-256 hash of the parsed data, and compares it to the previous run. If nothing changed, the site stays untouched. If a law changed, every affected page is regenerated and the change date above moves forward.
Even with automation, laws and regulations change constantly. Always verify the current text through the official link on each page before relying on it for legal advice, compliance, or filings.
Other Datasets
- CFR title metadata — latest issue date 2026-08-20 — eCFR
- State and territory code directories — 2026 — browse states
- Legal topic guides — reviewed annually — browse topics