Sample

One repository, names removed

One repository's commit history23 commits · newest first · Pacific time

02

Specifications

Full-History Codebases specifications
Formats	Git bundle, JSON, CSV, Patch
Delivery	Restricted data room, Sealed ZIP, Per-repository Git bundles
Cadence	Sealed release or custom refresh
Delivered as	One Git repository per codebase, with its full history
Contents	Source, tests, configuration, documentation, branches, tags and merges
History	Commit topology, timestamps, technical messages and reversions
Verification	Every bundle passes git fsck --strict and git bundle verify
Access	Public previews show selected structure and changes. Evaluation access and corpus delivery are arranged with the data team under agreed terms.
Built against	SWE-bench

What ships

Cloneable Repository Histories
One prerequisite-free Git bundle per codebase. Clone locally and inspect approved branches and tags, commit topology, timestamps, merges, technical messages, source, tests, configuration, and documentation.
Current Source Snapshots
Coherent repository trees rather than disconnected files, ready for cross-file retrieval, long-context understanding, test generation, and repository-level reasoning.
Manifests and Release Evidence
Stable pseudonymous IDs, exact hashes, repository-level counts, data cards, checksum manifests, sanitization summaries, and release evidence tie every claim back to the delivered bytes.

Fields

8 fields

Field	Description
repositories/{id}.bundleGit bundle	Prerequisite-free cloneable repository history with approved heads and tags.Example repositories/gh-repo-0064.bundle
MANIFEST.jsonJSON	Repository IDs, default refs, hashes, counts, quality disclosures, and release metadata.
DATA_CARD.mdMarkdown	Exact package-level counts, measurement definitions, and sanitization disclosures.
SHA256SUMStext	Checksum coverage for every other member of the archive.
audit/*.jsonJSON	History integrity, secret scanning, content scanning, semantic replay, and safety summaries.
source/directory · nullable	Current repository snapshot in the delivered package.
history/commits.csvCSV · nullable	De-identified commit index in the delivered package.Example 23 commit rows
history/patch-pairs/*.patchpatch · nullable	Representative de-identified historical changes in the delivered package.Example 5 patch pairs

Load it

The first commands after an approved delivery.

quickstart.sh

# After approved delivery, inspect the repository history
# Verify the supplied manifest and checksums before use.
shasum -a 256 -c SHA256SUMS
git bundle verify history/repository.bundle
git clone history/repository.bundle repo
git -C repo log --oneline --graph --all

03

Quality checks

4 checks

Git history integrity

Whether sanitization preserves the authentic source history one-to-one.

Compare source and target commit counts, dates, identities, messages, parent edges, refs and tags across every repository before release packaging.

Policy 2026-07-18.19 mapped every source commit to exactly one sanitized commit, with zero structural mismatches.

Extracted package verification

Whether the sealed archive and each repository bundle can be verified and cloned without hidden prerequisites.

Freshly extract the ZIP, verify member checksums, compare bundle hashes, run git fsck --strict and git bundle verify, and reconcile every included repository ID and ref.

Every bundle passed; zero package failures, traversal entries, duplicate members, encrypted members, symlinks or checksum mismatches.

Sanitized content and secret scan

Whether prohibited identity, contact, secret, private-path, sensitive-record or unsafe content survives in reachable history.

Layer primary and custom secret scanning with content, provenance, safety and complete reachable-blob review over the sanitized corpus and a fresh extraction.

Zero unresolved sanitized-content findings and zero sanitized secret-scan findings across every rewritten repository.

Repository preview integrity

Whether the displayed history and selected patch correspond to a coherent underlying repository.

Compare source/ byte-for-byte to bundle HEAD, validate commit rows and patch pairs, parse all JavaScript files, and resolve relative JavaScript and Solidity imports without network access.

117/117 source files match bundle HEAD; 23/23 normalized commit trees match the source history after disclosed redactions; 98/98 JavaScript files parse; zero relative imports are unresolved. Runtime tests were not executed because the exact Hardhat dependency tree and lockfile are unavailable.

Ground truth

What is correct	The sealed repository bundles themselves, their exact SHA-256 hashes, the package manifest, and the source-to-target rewrite ledger define the released corpus.
How it is established	Counts are reproduced directly from Git objects and extracted files. Bundle refs and hashes are reconciled to the sanitized mirrors; package members are checked against complete SHA256SUMS coverage; fresh extraction is scanned again.
Agreement	Independent round-eight review of the exact policy-2026-07-18.19 sealed bytes returned PASS with zero unresolved supported blockers. The review covered the packaged evidence and every unique reachable historical text blob.

How it is built

01
Inventory the complete source universe
Start from every mirrored repository, including empty ones, with its complete commit history.
02
Rewrite narrowly and deterministically
Apply redaction policy 2026-07-18.19 to remove principal identity, contributor contact details, credentials, sensitive records, private paths and unsafe payloads while preserving safe technical context, source, tests, documentation, timestamps, messages, branches, tags, merges and topology.
03
Reconcile every commit and ref
Verify that every source commit maps one-to-one to a sanitized commit, with zero date, identity, message, parent, ref-target or tag mismatches under the published rewrite policy.
04
Remove only empty and duplicate copies
Subtract empty repositories and conservatively supported duplicate copies. No repository is removed for rights, provenance, brand, quality or a confirmed safety issue.
05
Seal and independently review
Build cloneable bundles, manifests, checksums and audit summaries; scan fresh extractions; verify every bundle; then submit the exact sealed ZIP bytes for independent review. The review returned PASS with zero unresolved supported blockers.

04Software histories & tasks

05RequestReplies usually within one working day

Request a sample

We send real records in the format you would receive, with the field list and where each record came from. Access for evaluation is limited and covered by a mutual NDA.

ProductFull-History Codebases

Full-History Codebases