holistic compression sources · vendored · offline
The source vault behind CHCE.
Every third-party compressor, preprocessor, recompressor and entropy-coder reference the engine uses, vendored flat in one tree. A clone is the whole source tree — no submodules, no registry, no network at build time.
What this is for
A compression engine that fetches its dependencies at build time cannot be audited, cannot be built offline, and cannot promise that the bytes it produced last year are the bytes it produces today. Every source here is vendored at a revision that was tested — and the register below is the machine-readable list consumers read, not documentation that drifts from it.
The register — 55 sources, 14 categories
| Category | Sources |
|---|---|
| Entropy / Final-Stage | 6 |
| LZ / Match Finder | 7 |
| Context-Mixing | 5 |
| BWT | 2 |
| Numeric / Structured | 2 |
| Fast / Asymmetric | 7 |
| Preprocessors | 3 |
| Recompressors | 8 |
| Fast Deflate | 2 |
| Executable Packers | 2 |
| Embedded | 2 |
| Discovery / Reference Lists | 2 |
| Additional / Experimental | 5 |
| Pending Additions (queued for next commit) | 2 |
read from SOURCES in the repository
The constraints
| Rule | What it forbids |
|---|---|
| Offline only | No neural networks, no model files, no GPU runtimes. Context-mixing compressors such as zpaq and paq8px are pure algorithms — not AI, and fully offline. |
| Single source of truth | No submodules and no nested .git directories.
All sources are vendored flat. |
| Licence-audited | Nothing enters without its licence recorded in the register and its full text kept beside it. |
Where the vault stands
0 of 55 sources are pinned, and 13 licences are still
marked verify. The register carries a pin column and every row
reads TBD until the first build records a commit.
That matters because the whole argument for vendoring is reproducibility: until a row has a
pin, a consumer building from it is trusting main, which is the thing this vault
exists to avoid. It is stated here rather than left for a consumer to discover.
How it is consumed
Not as a dependency manager would do
it. Consumers pull the vault with git subtree into their own vendor/
and build from the pinned tree — so a consumer's build is reproducible without a network and
without trusting a registry.
# one tree, vendored into the consumer
git subtree add --prefix vendor/hcs \
https://github.com/drsamonline/HCS main --squash
Support the work
Free to use, and it stays free
Everything here is free, offline and accountless. If it earned its keep, there are a few ways to say so — pick whichever is easiest where you are.