Skip to main content

Repository launch checklist

Prove that a new repository is ready for public work.

Complete each applicable item. File checks do not prove external settings.

Repository

  • The repository uses the correct starter profile.
  • Package names, repository links, and the final domain are consistent.
  • No declared placeholder remains.
  • The MIT license and Lupinum company ownership are correct.
  • README.md, AGENTS.md, MAINTAINING.md, CONTRIBUTING.md, SECURITY.md, CLAUDE.md, and docs/WRITING.md have one responsibility.
  • pnpm verify, pnpm docs:build, pnpm audit:all, and pnpm release:verify pass where applicable.

GitHub

  • main is protected and required checks are current.
  • Workflow permissions are explicit and minimal.
  • GitHub Actions can create pull requests when the version workflow needs it.
  • CodeRabbit, Renovate, Dependabot alerts, and package previews are active.
  • The bug, documentation, feature, PR, and security paths work.
  • A real pull request has exercised all integrations.

npm libraries

  • The npm environment permits only main and requires a reviewer.
  • No NPM_TOKEN exists.
  • Every public package appears in certification, preview, and publication manifests.
  • The first bootstrap and later trusted-publication procedures are documented.

Documentation deployment

  • The Vercel Root Directory is docs.
  • The cold build works without local generated files.
  • The canonical domain and DNS resolve to production.
  • The real Plausible script ID is committed exactly once.
  • Discord, legal notice, privacy, and feedback links work.
  • The production acceptance checklist passes.