ShipForge Launch Doctor

Launch readiness report

This redacted, synthetic artifact demonstrates the structure of a human-verified Founding Beta report. It contains no customer data, real repository content, credentials, or production findings.

App[Sample app — redacted]

Review IDSAMPLE-LD-001

ReviewedSeptember 3, 2026

Launch score72/100

Executive summary

Recommendation: Hold store submission until the critical secret-handling issue is resolved and verified. The sample app is otherwise close to a test-track release.

Scope: Security, authentication, monetization, privacy/store readiness, and launch operations. Findings below are synthetic examples.

Findings

LD-001 — Client bundle references a privileged service credential

Critical

Business impact

An extracted credential could allow unauthorized use, unexpected provider charges, or access to protected operations.

Exact evidence

[REDACTED]/lib/services/example_client.dart:42–48
const privilegedCredential = "[SAMPLE_REDACTED_VALUE]";

Confidence

0.98 — high-confidence deterministic match, confirmed by a human reviewer.

Recommended action

Rotate the credential, move the privileged operation behind a server boundary, and ship only a public client identifier. Re-run secret scanning before release.

Review status

Confirmed.

LD-002 — Purchase entitlement appears to trust local state

High

Business impact

A modified client could unlock paid access without a verified store transaction, reducing revenue and creating support disputes.

Exact evidence

[REDACTED]/lib/billing/entitlement_gate.dart:18–31
Access decision reads a local boolean; no server receipt check is visible.

Confidence

0.89 — the reviewed path is incomplete, but no server-verification call was found in the submitted scope.

Recommended action

Verify receipts or provider entitlements on a trusted server, then return a short-lived entitlement decision to the app.

Review status

Confirmed within submitted scope.

LD-003 — Account-deletion completion cannot be verified

Review required

Business impact

If deletion stops at the UI, store review or privacy requests may fail and retained account data may exceed user expectations.

Exact evidence

[REDACTED]/lib/settings/delete_account.dart:55–70
UI confirmation is present. The server handler was outside the submitted files.

Confidence

0.54 — evidence is insufficient to assert that deletion is missing.

Recommended action

Provide the server deletion handler or production test evidence. Verify deletion across auth, profile, storage, and processor records.

Review status

review_required — not counted as a confirmed defect until evidence is supplied.

Five-dimension score

Dimension	Score	Reviewer note
Technical build	68	Resolve the credential exposure before release.
Store readiness	82	Metadata is mostly complete; verify deletion evidence.
Monetization	58	Server-side entitlement verification is required.
Privacy & legal	74	Deletion backend evidence remains incomplete.
Post-launch operations	79	Crash reporting and rollback notes are present.

Re-scan delta

Initial score

Current sample score

72 (+11)

Verified change: Two high-severity sample findings were resolved. One critical finding remains open. The review-required item remains pending evidence.