nestjs/nest auditDelivery risk audit on GitHub · Analysed 15 Jul 2026 · GitHub
This delivery risk audit analyses the last 90 days of public commit history for nestjs/nest. It identifies files that concentrate bug-fix activity, measures revert frequency as a signal of release instability, and maps contributor spread to highlight knowledge concentration risk. The risk score weights bug-fix commits and reverts for each file, with higher scores indicating files that have required the most corrective attention in the analysed period.
| File | Risk | Bug Commits | Reverts | Commit touches |
|---|---|---|---|---|
| package.json | 60 | 6 | 0 | — |
| sample/05-sql-typeorm/package.json | 60 | 6 | 0 | — |
| sample/13-mongo-typeorm/package.json | 50 | 5 | 0 | — |
| package-lock.json | 40 | 4 | 0 | — |
| sample/07-sequelize/package.json | 40 | 4 | 0 | — |
| sample/12-graphql-schema-first/package.json | 30 | 3 | 0 | — |
| sample/17-mvc-fastify/package.json | 30 | 3 | 0 | — |
| sample/31-graphql-federation-code-first/gateway/package.json | 30 | 3 | 0 | — |
| sample/31-graphql-federation-code-first/posts-application/package.json | 30 | 3 | 0 | — |
| sample/31-graphql-federation-code-first/users-application/package.json | 30 | 3 | 0 | — |
| sample/32-graphql-federation-schema-first/gateway/package.json | 30 | 3 | 0 | — |
| sample/32-graphql-federation-schema-first/posts-application/package.json | 30 | 3 | 0 | — |
| sample/32-graphql-federation-schema-first/users-application/package.json | 30 | 3 | 0 | — |
| sample/33-graphql-mercurius/package.json | 30 | 3 | 0 | — |
| Readme.md | 20 | 2 | 0 | — |
| packages/platform-ws/package.json | 10 | 1 | 0 | — |
| sample/01-cats-app/package.json | 10 | 1 | 0 | — |
| sample/02-gateways/package.json | 10 | 1 | 0 | — |
| sample/03-microservices/package.json | 10 | 1 | 0 | — |
| sample/04-grpc/package.json | 10 | 1 | 0 | — |
✨ AI Interpretation
Get a plain-English explanation of what these metrics may (and may not) mean for delivery risk.
View interactive reportThis analyses public commit history. Connect a private repo to see bug-fix hotspots, ownership risk and delivery friction on the code your team ships every day. Read-only, no source code stored.
Audit your private repo, free →