Community

Get Involved

• GitHub Discussions - Questions, ideas, and general discussion
• GitHub Issues - Bug reports and feature requests (per-package repos)
• npm - All published packages

Contributing

We welcome contributions to any nestarc package. Here's how to get started:

1. Pick a package

Each package lives in its own repository under the nestarc organization:

Package	Repository
tenancy	nestarc/nestjs-tenancy
safe-response	nestarc/nestjs-safe-response
audit-log	nestarc/nestjs-audit-log
feature-flag	nestarc/nestjs-feature-flag
soft-delete	nestarc/nestjs-soft-delete
pagination	nestarc/nestjs-pagination
idempotency	nestarc/nestjs-idempotency
outbox	nestarc/outbox
webhook	nestarc/webhook
api-keys	nestarc/api-keys
data-subject	nestarc/data-subject
jobs	nestarc/jobs

2. Development workflow

# Clone the repo
git clone https://github.com/nestarc/nestjs-<package>.git
cd nestjs-<package>

# Install dependencies
npm install

# Run tests
npm test

# Build
npm run build

3. Submit a PR

• Fork the repository
• Create a feature branch from main
• Write tests for your changes
• Ensure all tests pass
• Submit a pull request with a clear description

Roadmap

Roadmap items are grouped by current product focus. Nestarc core stays focused on SaaS backend primitives; experimental developer tools live under Labs until they are proven enough to become part of the main product direction.

Stage	Items
Now	Webhooks Cloud beta, package docs sync, API reference expansion
Next	@nestarc/rbac, Webhooks onboarding, examples
Later	metering, quota, entitlements
Exploring	Labs: mcp-guard, experimental developer tools

Core vs Labs

Core roadmap items are packages, docs, examples, and Cloud workflows that directly support production SaaS backends. Labs items are experiments that may be useful to developers, but they are intentionally separate from the core roadmap until their fit is clear.