ModRelease Studio

Release preflight for game mods & mod packs

Scan a folder or ZIP before you publish. Catch packaging risks, leaked secrets, and missing metadata — and share a clean report with your players.

⬇ Download ☕ Buy me a coffee Contact
CI status Latest release MIT license
What it checks
One command, repeatable checks, a readable report.

Packaging risks

  • Unsafe archive paths & path collisions
  • Case-only collisions
  • Unexpectedly large or junk files
  • Missing required files (README, LICENSE…)

Secrets & safety

  • Private keys, API keys, tokens
  • GitHub / Slack / Discord tokens
  • AWS access-key IDs
  • Best-effort scan — review findings yourself

Mod metadata

  • Paradox descriptor.mod checks
  • Localization YAML headers & keys
  • Missing supported_version
  • SHA-256 fingerprint of each build
How it works
Local-first: your mods never leave your machine unless you upload the report.
modrelease scan output catching a leaked token, a bad localization header, and a missing supported_version 
# Before your first release
modrelease scan ./my-mod --md-out release-report.md

# Compare two builds
modrelease compare ./previous-build ./candidate-build

# Or gate releases in CI with the GitHub Action
- uses: GhosTnever-lkm/modrelease-studio-action@v1

Exits with code 0 (ready), 1 (release-blocking findings), or 2 (invalid input). Requires Python 3.11+, standard library only.

Pricing

Core — Free

MIT-licensed CLI. Scan, compare, JSON/Markdown reports. Run locally or in CI.

Pro — Coming soon

Custom rule packs, team reporting, release dashboards. Join the waitlist via contact.

Services

Custom checks, release audits, and gate setup for your mod distribution.

View on GitHub
Contact

Questions, custom checks, or a release audit? Reach out by GitHub or email.

GitHub profile Open an issue Email