nunu
Nunu is a CLI scaffolding tool for Go applications that bundles popular ecosystem libraries (Gin, GORM, Wire, Zap) into a pre-configured layered architecture. It reduces boilerplate setup for new Go projects and supports code generation for handlers, services, and models.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | go-nunu/nunu |
| Owner | go-nunu |
| Primary language | Go |
| License | MIT — OSI-approved |
| Stars | 2.6k |
| Forks | 205 |
| Open issues | 2 |
| Latest release | v1.1.3 (2025-08-11) |
| Last updated | 2026-04-26 |
| Source | https://github.com/go-nunu/nunu |
What nunu is
Nunu provides a structured project template and CLI commands for Go applications using dependency injection (Wire), HTTP routing (Gin), ORM (GORM), logging (Zap), configuration management (Viper), and testing utilities. It enforces a modular layered architecture (handler/service/repository/model) with hot-reload support during development.
Get the nunu source
Clone the repository and explore it locally.
git clone https://github.com/go-nunu/nunu.gitcd nunu# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Go 1.19+ is required; verify environment setup and GOBIN configuration for CLI availability after `go install`.
- The generated project structure enforces a specific layered pattern; teams must accept or commit to refactoring if internal architecture differs significantly.
- Wire-based dependency injection requires regeneration after model/service changes; integrate `nunu wire` into build pipelines to avoid manual compilation errors.
- Default templates pull from GitHub; environments with network restrictions may need custom template repositories (Gitee mirrors are documented).
- Bundled libraries (Gin, GORM, Zap, Viper) versions are set at generation time; maintenance and upgrades are manual afterward.
When to avoid it — and what to weigh
- Extreme Minimalism or Functional Architectures — Projects requiring ultra-lightweight dependencies or functional/domain-driven patterns radically different from the bundled layered architecture.
- Non-Standard Database or Async Patterns — Applications heavily reliant on GraphQL, gRPC, event streaming, or NoSQL-only stacks where the default GORM + SQL focus is misaligned.
- Highly Specialized or Legacy Integration — Systems with rigid external dependency requirements or legacy codebase patterns that conflict with Nunu's opinionated structure.
- Production Code Requiring Extensive Customization — If your team needs to heavily modify or remove core bundled libraries post-generation, the time saved by scaffolding may be offset by refactoring overhead.
License & commercial use
Nunu is released under the MIT License, which is a permissive OSI license allowing commercial use, modification, and distribution with minimal restrictions (retain license and copyright notice).
MIT License permits commercial use without restriction. However, ensure compliance with licenses of all bundled dependencies (Gin, GORM, Wire, Zap, etc.) in your commercial product. Conduct a dependency audit before production deployment.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
Nunu itself is a scaffolding tool and does not execute untrusted code. Security posture depends on: (1) versions of bundled libraries (Gin, GORM, JWT, Casbin) at generation time; (2) user implementation of handlers/middleware; (3) environment configuration (secrets management via Viper). No built-in secrets rotation, encryption, or hardening guides. Teams must implement authentication (JWT provided), authorization (Casbin included), and input validation independently. Conduct dependency vulnerability scan after project generation.
Alternatives to consider
Buf (Protocol Buffers + gRPC scaffold)
If building gRPC microservices rather than REST APIs; Buf is more specialized for RPC-first architectures and less opinionated about layered structure.
echo or chi + manual setup
For teams preferring minimal frameworks or routing libraries; manual composition offers more control but requires more boilerplate and discipline.
Ent (Entity Framework for Go)
If ORM design and type-safe graph queries are paramount; Ent is more sophisticated than GORM but steeper learning curve and less common in Go ecosystem.
Build on nunu with DEV.co software developers
Nunu reduces boilerplate setup for Go applications. Our team can help evaluate whether Nunu fits your architecture, audit dependencies, and integrate it into your CI/CD pipeline.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
nunu FAQ
Can I customize the generated project structure after creation?
Does Nunu support databases other than MySQL?
How is dependency injection managed?
Is Nunu suitable for production?
Work with a software development agency
From first prototype to production, DEV.co delivers software development services around tools like nunu. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across mcp servers and beyond.
Ready to Accelerate Go Development?
Nunu reduces boilerplate setup for Go applications. Our team can help evaluate whether Nunu fits your architecture, audit dependencies, and integrate it into your CI/CD pipeline.