nestarc Open-Source 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 |
| pagination | nestarc/nestjs-pagination |
| soft-delete | nestarc/nestjs-soft-delete |
| idempotency | nestarc/idempotency |
| audit-log | nestarc/nestjs-audit-log |
| api-keys | nestarc/api-keys |
| feature-flag | nestarc/nestjs-feature-flag |
| rbac | nestarc/rbac |
| outbox | nestarc/outbox |
| inbox | nestarc/inbox |
| jobs | nestarc/jobs |
| webhook | nestarc/webhook |
| data-subject | nestarc/data-subject |
Labs and developer tooling live separately from the main SaaS package list:
| Tool | Repository |
|---|---|
| mcp-guard | nestarc/mcp-guard |
2. Development workflow
bash
# Clone the repo
git clone https://github.com/nestarc/<repo>.git
cd <repo>
# Install dependencies
npm install
# Run tests
npm test
# Build
npm run build3. 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
The open-source packages can be adopted independently or composed into an application workflow. The roadmap focuses on package compatibility, integration guidance, and operational behavior that can be verified against published releases.
| Area | Focus |
|---|---|
| Package integration | Maintain the async delivery reference workflow and document the supported outbox → jobs delivery boundary |
| Compatibility | Keep runtime requirements, package version boundaries, and migration guidance aligned with published releases |
| Operations | Document retry, recovery, retention, tenant isolation, and lifecycle hooks with their limitations |
| Documentation | Keep generated API references and package adoption guidance aligned with the catalog |
Package scope
The SaaS packages are independently installable open source and run in the application's own environment. Labs and developer tools, including @nestarc/mcp-guard, are listed separately from the main SaaS package catalog.