Skip to content

Latest commit

 

History

History
19 lines (16 loc) · 1.08 KB

TRUST.md

File metadata and controls

19 lines (16 loc) · 1.08 KB

Procedure Overview

  1. Frontend calls Modrinth API to retrieve information about current modpack versions
  2. User selects version and other install parameters
  3. Frontend sends modpack bundle URL alongside verification material to backend
  4. Backend downloads modpack bundle and verifies it
  5. Backend removes any previously installed files
  6. Backend downloads mods as specified by manifest and verifies their SHA512 hashes
  7. Backend installs misc. files contained in bundle
  8. Backend queries Fabric Meta to install Fabric version requested by manifest
  9. Backend creates launcher profile and writes install metadata to file

Trust & Security

  • Modpack bundle is built from source and signed by Github Actions using cosign
  • Source and modpack bundle includes hashes for all their required external files
  • Backend restricts download URLs for modpack manifest and external mods
  • Backend calls Verifier to verify modpack signature
  • Verifier verifies modpack was built from source using Github Actions, as part of a release pipeline