Know what’s
in your mods.

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.

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.

Choose only what you need.

1. Download the Windows x64 beta from GitHub and run Observe-Setup.exe.
2. No plugins are selected by default. Select Cities II mod observer for the UVM bridge. Windows 10/11 and Microsoft Edge WebView2 Runtime are required.
3. Optionally select Windows forensic logging for Microsoft Sysmon and PowerShell logs. Windows requests administrator approval; review the Sysmon license in the installer. Existing Sysmon rules are retained.
4. Install the UVM 0.6.1, following its instructions to avoid loading a second UVM copy. Run Observe and Cities: Skylines II. The local connection retries automatically. Optional sign-in startup keeps Observe available after restarting Windows.

Follow the evidence.

Open Cities II mods in Observe or Options → Unified Verified Mods → Scan in the game. A green connection check confirms a recent exchange.

Code-only and loaded-only filters synchronize both ways. Expand a mod to inspect its last build result, loaded assemblies, compiled API references and any cooperative activity reports.

Windows process, file and network events describe the shared game process. They do not establish which mod caused an event. A reproduced build is not a safety audit. AI comparison of a mod’s description and behavior is a future feature.