CITIES: SKYLINES II · PUBLIC BUILD EVIDENCE

Know what’s
in your mods.

Connect installed files to public source code.
Inspect signed build results from GitHub accounts.

Check your files ↗Become a verifier →

THE REGISTRY

Evidence you can inspect.

Loading registry…

MOD / RELEASEBUILD EVIDENCEGITHUB ACCOUNTS

Reproduced: a signed matching build Published: publisher’s hashes only Disputed: conflicting evidence

ON YOUR DEVICE

Check an installed mod.

Choose the mod’s package folder and enter its Paradox ID. File hashes are calculated in your browser. Only paths, hashes and the mod ID go to UVM.

Your DLLs and other file contents stay on your device. All executable files must be covered by the release’s evidence.

OPEN PARTICIPATION

One recipe. Public evidence.

FOR MODDERS

Describe the build you already use.

Keep the source public, commit the exact release and add uvm.json. Include every executable file in your package.

{
  "schema": 1,
  "platform": "paradox",
  "modId": 156779,
  "build": {
    "project": "FarmAutoFill.csproj",
    "configuration": "Release"
  },
  "output": ["FarmAutoFill.dll"]
}

Build locally, then publish a signed manifest. UVM stores the evidence; upload your normal mod package to Paradox.

FOR VERIFIERS

Rebuild it. Put your name to it.

Create a signing key, then prove your GitHub account by posting the generated proof as a public gist. Your private key stays with you.

uvm keygen
uvm key-proof
# Post uvm-key.json as a public gist
uvm register --gist <gist-url>

# In the release's source checkout:
uvm build --package ./package
uvm attest --manifest release.json \
  --package ./package

Only build source you have inspected and trust. A build command can execute code on your computer.

Get UVM

Use the command-line scanner or the Cities: Skylines II mod.

Download UVM 0.3 ↧Setup & API guide →