Hi HN,
I've been working on MonoGuard, a tool for analyzing monorepo
dependencies and architecture.
The problem: Managing large monorepos is painful. Dependency
conflicts, circular imports, and security vulnerabilities pile up
faster than you can track them. Existing tools are either too
complex to set up or prohibitively expensive.
The solution: Upload your package.json files (or entire project
zip), get a comprehensive analysis in 30 seconds. Files are
processed locally and automatically deleted for privacy.
Key features:
- Dependency conflict detection
- Circular dependency analysis
- Security vulnerability scanning
- Architecture validation
- Bundle impact analysis
Built with Go backend + Next.js frontend, deployed on
Railway/Vercel.
The free tier should cover most individual developers. Enterprise
features for teams coming soon.
Would appreciate any feedback from the community!
Live demo: https://mono-guard-frontend.vercel.app/
Quick clarification on how MonoGuard differs from existing tools:
Most dependency tools (npm audit, syncpack, etc.) focus on immediate issues - version conflicts, security patches, etc. MonoGuard looks at the bigger picture: is your monorepo architecture actually healthy?
Think of it as the difference between a health checkup vs. architectural assessment. We're not replacing your existing tools, we're adding the strategic layer on top.
Perfect for teams with 10+ packages who want to catch architectural debt before it becomes expensive to fix.
Quick clarification on how MonoGuard differs from existing tools:
Most dependency tools (npm audit, syncpack, etc.) focus on immediate issues - version conflicts, security patches, etc. MonoGuard looks at the bigger picture: is your monorepo architecture actually healthy?
Think of it as the difference between a health checkup vs. architectural assessment. We're not replacing your existing tools, we're adding the strategic layer on top.
Perfect for teams with 10+ packages who want to catch architectural debt before it becomes expensive to fix.