The Silo catalog

One record per mod. Two sources. Checked against the published build.

Silo brings ModHub and GitHub together into one record for each Farming Simulator 25 mod, with the latest version found across both, and hashes each build from its source. So an installed mod can be checked against the build its source published. That is what the Verified build badge means.

Browse the catalog Get Silo

mods indexed: …
ModHub and GitHub listings: …
categories: …

Live from the catalog when the page loads.

Mods scatter. The truth gets fuzzy.

A mod lives on ModHub, and its author ships newer builds on GitHub. Which is the latest? Is the file you downloaded the one the author actually published, or was it repacked with something extra? The catalog answers both.

One record per mod

A mod's ModHub and GitHub listings resolve to one record, so you see the latest version found across both.

Provenance, not a virus scan

We hash published builds. Silo hashes your installed copy on your computer and compares: a clean match, or the exact files that differ. It confirms what a mod is. It doesn't guess intent.

What's covered

An hourly job refreshes versions and metadata, most popular mods first. Silo can only verify ModHub builds it hashed before it paused downloads from GIANTS' servers (mod files and new cover images). ModHub versions and details still update, so update checks work as usual. GitHub builds are verified as usual.

What you'll see in Silo and on Browse

Verified build Your copy matches the published build byte for byte.
Modified (2 files) Your copy differs from the published build; Silo lists the files.
Unverified The catalog has no published build on file to compare against yet.

Silo indexes. It doesn't host.

Silo indexes public mod information and links back to each source. It does not host, mirror or redistribute mod files. Downloads always go to the original source, whose own terms apply.

Our catalog server keeps cover images and integrity hashes it cached earlier, ModHub ones included. We keep those to show what the full platform can do, should GIANTS allow us an official feed. We're going to ask GIANTS for that permission. Until they answer, the server fetches nothing new from GIANTS' CDN, and we'll remove the ModHub cache if GIANTS asks us to.

For mod authors

Help us get your builds right.

Provenance is only as good as its source of truth, and no one knows a mod's real build better than the person who made it. We'd like mod authors to be able to confirm their own builds. There's no way to do that yet. When Silo has your published build on file, players can check whether their copy matches it.

If your mod is listed wrongly, or you'd rather it wasn't listed, tell us and we'll fix it: open an issue on GitHub or email legal@hllmr.com. See also Copyright & Takedown.

For developers

A public read API.

The catalog is served by SiloAPI, a public, read-only HTTP API. No key, no account. It's rate-limited, so please be a good citizen. It aggregates public metadata and links back to sources.

Base: https://silo-api.hllmr.com

GET /stats
GET /categories
GET /mods?q=&category=&sort=&limit=&offset=
GET /mods/:id
GET /mods/:id/manifest?version=
POST /mods/lookup
GET /facets
GET /img/:id

The Browse page is built entirely on these endpoints.

For nerds

The whole system, by the numbers.

Aggregate counts only. There's no account and no telemetry, and the app contacts the catalog only when you search Browse, open a mod's details, check for updates or verify a mod. Traffic numbers come from our server access logs, which keep IP addresses for 30 days (see the privacy policy). Small numbers are shown as they are.

Downloads by release

… installer and app-package downloads

Release	Downloads	Share

Installer and app-package files only (.exe, .msi, .dmg, .AppImage, .deb, .rpm).

SiloAPI traffic

Window	Queries	Unique clients
1h	…	…
24h	…	…
5d	…	…
30d	…	…
total	…	–

30-day reach

Silo app clients: …
Browse visitors: …
Site visitors: …

Counted from our server access logs. We publish only the totals.