The dataset viewer is not available because its heuristics could not detect any supported data files. You can try uploading some data files, or configuring the data files location manually.
RPM repo per-file sha256 bloom filters
Membership filters over the sha256 of every file installed by every package in an RPM repository, one filter per repo family, all built by the same pipeline: repo metadata (primary.xml) publishes each RPM's exact header byte range, one HTTP range-GET per RPM fetches the header alone, and the FILEDIGESTS tag inside holds per-file sha256. No package contents are ever downloaded — ~2.5 GiB of headers covers ~76k Fedora packages.
| filter | keys | size | coverage |
|---|---|---|---|
fedora.sha256.bloom |
6,716,906 | 15 MiB | Fedora 44 Everything release + updates, x86_64 (2026-08-01) |
rpmfusion.sha256.bloom |
78,810 | 188 KiB | RPM Fusion free + nonfree, Fedora 44 release + updates (2026-08-02) |
vscode.sha256.bloom |
122,143 | 288 KiB | Microsoft VS Code yum repo, all published RPM versions (2026-08-02) |
All keys are lowercase hex sha256, p = 1e-4. The digest facts originate in each repo's public metadata; this compilation is CC0.
Rebuild
Both scripts are in this repo (httpx[http2] + zstandard needed
for the harvester); minutes per repo family against an HTTP/2
mirror, $0. Point fedora_headers.py at any RPM repo base URLs:
./fedora_headers.py \
https://mirror.aarnet.edu.au/pub/fedora/linux/releases/44/Everything/x86_64/os \
https://mirror.aarnet.edu.au/pub/fedora/linux/updates/44/Everything/x86_64 \
> digests.hex
sort -u digests.hex -o digests.hex
./dcso_bloom_build.py fedora.sha256.bloom sha256 digests.hex
For rpmfusion: the free (releases + updates) and nonfree trees on
any RPM Fusion mirror. For vscode:
https://packages.microsoft.com/yumrepos/vscode. The same command
works for EPEL, openSUSE-style repos, or anything else that ships
rpm:header-range in its primary.xml.
Format
DCSO bloom filter format (github.com/DCSO/bloom), the same format
CIRCL publishes hashlookup in: 48-byte little-endian u64 header
(version, n, p, k, m, N) followed by the bit array. Keys are hex
digest strings. Any DCSO-compatible reader works.
Membership answers are probabilistic: p = 1e-4 false-positive rate, no false negatives. Confirm anything important against the source.
- Downloads last month
- 48