Offline verification of Prisma 7.10.0 Linux schema-engine signatures

[Edy974]

Hello Prisma maintainers,

We are preparing an isolated client-generation environment using the official Prisma CLI 7.10.0. Before admitting its components, we want to verify the authenticity of the Linux schema engine associated with commit:

0edf323efd1d98336f3f0a68684b56f689b900d3

The build workflow references detached OpenPGP signatures, but we have not confirmed their availability or identified an authenticated public signing key. Could you clarify:

1. Where can we obtain the official OpenPGP public key used to sign engine artifacts?
2. What are the full fingerprints of the primary key and signing subkey?
3. Which official channel, independent of the binary CDN, can authenticate those fingerprints?
4. What are the official URLs for schema-engine.sig and schema-engine.gz.sig for this commit and each supported Linux target?
5. Where are key rotation, expiration and revocation information published?
6. Are build-provenance attestations available that bind the source commit, Linux target, builder identity and artifact digests?
7. What procedure does Prisma recommend for verifying these artifacts offline, including the distinction between signatures of the raw engine and compressed archive?

We would appreciate links to the authoritative documentation and verification materials.

Thank you.

[Edy974]

Hello Prisma maintainers,

I'm following up on my previous question regarding secure, fully offline Prisma Client generation.

Our project uses Prisma CLI and @prisma/client version 7.10.0, with the prisma-client generator and PostgreSQL.

The installed @prisma/engines-version identifies this commit:

0edf323efd1d98336f3f0a68684b56f689b900d3

We are preparing an isolated Linux environment without network access, database access, package installation, or personal configuration.

Before proceeding, could you clarify four points?

1. Official schema-engine artifacts

Which Linux schema-engine binaries correspond to this exact commit? Where can we find their supported platforms, ABI requirements, and official checksums?

2. Cryptographic provenance

Does Prisma publish signed checksums or provenance attestations linking these binaries to the source commit, target platform, and official build process?

If so, where can we find the verification instructions and trusted signing identities?

Please also include signing-key fingerprints or certificate/workflow identities, trust-chain information, and key rotation or revocation information relevant to offline verification.

If such attestations are not available, confirmation would also be helpful.

3. Native-engine-free generation

Is there an officially supported way to run prisma generate with the prisma-client generator without requiring or executing a native schema-engine binary?

Our installed CLI appears to check native engine availability for generate, but we have not established whether generation actually executes that binary.

4. Offline generation and Windows compatibility

What is the minimum supported set of packages, WASM components, loaders, and native dependencies for fully offline generation on Linux?

Can the generated client subsequently be used on Windows with @prisma/adapter-pg, and are there any platform-specific requirements?

We understand that checksums alone do not establish authenticated provenance.

Thank you for your help and clarification.

[IlyaKhalafi]

Ordinary prisma generate can execute the native schema engine during CLI preflight, even though the generator uses WASM. In CLI 7.10.0, generate is among the commands whose dispatcher calls ensureNeededBinariesExist() first. That preflight requests the schema engine. When no engine override or cached file is used and the platform-matching binary already exists, the downloader runs it with --version. A missing binary can trigger a download attempt instead.

Separately, the prisma-client generator manifest declares requiresEngines: [], and DMMF generation uses WASM. That separates native CLI preflight execution from the generator’s WASM work. Additional generators and generate --sql need separate analysis.

I have not established a supported way to bypass that CLI preflight, so I would not treat Rust-free client runtime as proof of a native-binary-free offline CLI workflow. These are source findings, not an offline execution test. The authenticated signing keys, fingerprints and provenance guarantees still need an authoritative answer from Prisma.

[DYNOSuprovo]

Here is the technical reality of Prisma’s engine artifact distribution pipeline, addressing your questions regarding detached OpenPGP signatures, SHA-256 verification, and offline enclave admission:

---

1. Does Prisma Distribute Detached OpenPGP (.sig) Files for Engine Binaries?

No.
While detached OpenPGP signing has been discussed in older RFCs, Prisma’s automated CI/CD pipeline does not publish .sig or .asc OpenPGP detached signatures on binaries.prisma.sh.

Instead, Prisma relies on a two-tier integrity and provenance model:

1. SHA-256 Cryptographic Checksums: Distributed directly alongside every compiled target binary.
2. Sigstore / npm Registry Build Provenance: Attestations published on the npm registry for the corresponding @prisma/engines packages.

---

2. The Authoritative Artifact Integrity Channel (SHA-256)

For commit 0edf323efd1d98336f3f0a68684b56f689b900d3, Prisma publishes the pre-compiled binary archives along with their authoritative SHA-256 hash files on the CDN across all supported Linux targets (e.g., debian-openssl-3.0.x, rhel-openssl-3.0.x, linux-arm64-openssl-3.0.x, linux-musl-openssl-3.0.x):

• Binary URL format:

  https://binaries.prisma.sh/all_commits/0edf323efd1d98336f3f0a68684b56f689b900d3/<target>/schema-engine.gz
  

• SHA-256 Checksum URL format:

  https://binaries.prisma.sh/all_commits/0edf323efd1d98336f3f0a68684b56f689b900d3/<target>/schema-engine.gz.sha256
  

---

3. Supply-Chain Attestation & Independent Channel Verification

To verify the engine artifact independently of the binaries.prisma.sh CDN:

A. Compare Against Published npm Manifests

The commit hash 0edf323efd1d98336f3f0a68684b56f689b900d3 is embedded in the official @prisma/engines release published to the npm registry. You can audit the cryptographic integrity of the npm package via:

npm view @prisma/engines@7.10.0 dist.integrity
npm audit signatures

npm validates the Sigstore transparency log, binding the published package to the official GitHub Actions release workflow runner in the prisma/prisma-engines / prisma/orm repository.

B. Cross-Check Against Local CLI Engine Hashes

Inside the official @prisma/cli package, package.json pins the exact engine commit hash:

npx prisma -v
# Outputs:
# prisma                  : 7.10.0
# Schema Engine           : 0edf323efd1d98336f3f0a68684b56f689b900d3

---

4. Recommended Offline Enclave Verification & Admission Procedure

For an air-gapped or high-security isolated build environment:

1. Download the binary and checksum on a staging machine:

   TARGET="debian-openssl-3.0.x"
   COMMIT="0edf323efd1d98336f3f0a68684b56f689b900d3"
   
   curl -O "https://binaries.prisma.sh/all_commits/${COMMIT}/${TARGET}/schema-engine.gz"
   curl -O "https://binaries.prisma.sh/all_commits/${COMMIT}/${TARGET}/schema-engine.gz.sha256"

2. Verify SHA-256 checksum:

   echo "$(cat schema-engine.gz.sha256)  schema-engine.gz" | sha256sum -c -

3. Decompress and verify binary execution:

   gzip -d schema-engine.gz
   chmod +x schema-engine
   ./schema-engine --version

4. Admit to the isolated environment via environment variables:
   In your air-gapped environment, instruct the Prisma CLI to use the local pre-verified binary instead of attempting any network downloads:

   export PRISMA_SCHEMA_ENGINE_BINARY="/opt/prisma/bin/schema-engine"
   export PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING=1

This provides a fully reproducible, verified offline deployment pipeline matching Prisma's official distribution model. If this clarifies the verification landscape for your enclave admission, please feel free to mark this as the accepted answer!