Spergs, LLC

← All products

LibWorld

In progress

Mirror, cache, and preserve your software supply chain.

About LibWorld

LibWorld stands in front of the ecosystems your builds depend on — apt, pip, npm, git, cargo, go, maven, rubygems, nuget, cocoapods, the Docker Registry API, plain files and OS images — proxies them, caches every artifact it fetches, and serves it from inside your network. A deleted package, an upstream outage, or a flaky mirror no longer breaks the build you need today or the one you need to reproduce in five years.

Pin artifacts, prefetch whole dependency trees before going offline, and garbage-collect by age and last use while protecting what you have pinned. Pull-audit logs record what was pulled, pinned, deleted or refused, and orphaned blobs the catalog lost track of can be found and adopted rather than quietly leaked. Artifacts are checked against what upstream published rather than merely hashed on arrival — for apt that means walking the signed Release chain down to each package, and the provenance of the check is recorded per catalog row — and a snapshot freezes a named set of what the mirror holds, protected from collection and checkable byte for byte years later.

It is a small set of C++ services built from vendored dependencies with no system-package requirements: a Boost.Beast proxy/mirror with thirteen backends, a Postgres catalog of everything mirrored, S3-compatible blob storage, a self-hosted git forge with push-to-build, and a build service whose runners poll out — no inbound ports on build hosts — and resolve every dependency through the mirror, so builds are hermetic and each dependency gets catalogued as a side effect. Production is reached by promotion: a deploy target names the staging target it is promoted from, and the coordinator refuses to queue it unless that exact workspace passed staging and the artifact being installed is that staging build's. Self-hostable, MIT-licensed, host-native Ansible + systemd deploy, no Docker.

One thing it does not do, named here rather than implied: there are no write-once stores, so nothing at the storage layer stops a mirrored artifact being overwritten in place.

At a glance

  • Drop-in proxy + cache for thirteen ecosystems
  • Deterministic, reproducible, offline-capable builds
  • Prefetch to warm the cache before you go air-gapped
  • Retention/TTL + garbage collection, pull-audit logs
  • Self-hosted git forge, with push-to-build
  • Netboot a machine from checksum- and GPG-verified images
  • Artifacts verified against what upstream published
  • Named snapshots, frozen and protected from collection
  • Production reached by promotion, never by landing on it
  • Self-hosted C++ services, MIT-licensed

More from Spergs

Other independent software we ship, or are working on.