Open dApp

Repository

Open-source publication scope

What should be included in public frontend repository and what must be excluded before publish.

1. Include in public repository

  • `app/` routes, components, and styles.
  • `lib/` dApp integration helpers and contract bindings.
  • `public/` required frontend assets.
  • `README.md`, `RELEASE_CHECKLIST.md`, `OPEN_SOURCE_MANIFEST.md`.
  • Policy docs: `SECURITY.md`, `REPORTING.md`, `RULES_OF_USE.md`.
  • Build config: `package.json`, lockfile, TypeScript and Next config files.
  • Safe template env: `.env.example`.

2. Exclude from public repository

  • `.env` and any environment file with secrets/tokens.
  • Build outputs (`.next/`, coverage, local artifacts).
  • `node_modules/` and temporary local files.
  • Private deployment logs containing sensitive values.
  • Local-only folders not intended for frontend repo scope.

Publishing order

1) Verify env hygiene, 2) pass build gates, 3) update docs, 4) publish from clean branch.