The Tooling Inventory scanner maps your complete technology stack by analyzing package.json dependencies. It categorizes your tooling choices to support standardization initiatives, technology assessments, and migration planning.
Detection Categories
Frontend Frameworks
| Category | Detected Packages |
|---|
| React ecosystem | react, react-dom, @tanstack/react-query, zustand, jotai |
| Vue ecosystem | vue, pinia, @vue/... |
| Angular | @angular/core, @angular/cli |
| Svelte | svelte, @sveltejs/kit |
| Solid | solid-js, solid-start |
| CSS | tailwindcss, styled-components, @emotion/... |
Meta-Frameworks
| Framework | Detected Packages |
|---|
| Next.js | next |
| Nuxt | nuxt |
| Astro | astro |
| Remix | @remix-run/... |
| SvelteKit | @sveltejs/kit |
| Gatsby | gatsby |
Build Tools
| Category | Detected Packages |
|---|
| Bundlers | vite, webpack, esbuild, rollup, parcel |
| Transpilers | typescript, @babel/core, swc |
| Task runners | turbo, nx, lerna, gulp |
Backend
| Category | Detected Packages |
|---|
| HTTP frameworks | express, fastify, hono, koa |
| Full frameworks | @nestjs/core, adonisjs |
| API | @trpc/server, graphql, @apollo/server |
| Serverless | serverless, sst, @aws-sdk/... |
Data & ORM
| Category | Detected Packages |
|---|
| ORM/Query builders | prisma, drizzle-orm, typeorm, sequelize, knex |
| Database clients | pg, mysql2, mongodb, redis |
| Validation | zod, yup, joi, valibot |
Testing
| Category | Detected Packages |
|---|
| Test runners | vitest, jest, mocha, ava |
| E2E | playwright, cypress, puppeteer |
| Utilities | @testing-library/..., msw, supertest |
Observability
| Category | Detected Packages |
|---|
| Error tracking | @sentry/node, @sentry/react |
| Monitoring | dd-trace, newrelic |
| Logging | pino, winston, bunyan |
| OpenTelemetry | @opentelemetry/... |
Use Cases
Technology Standardization
Identify teams using different tools for the same purpose:
vg scan --format json | jq '.toolingInventory'
Example finding: Three projects using different HTTP frameworks (Express, Fastify, Hono).
Migration Planning
Before framework migrations:
- Audit current tooling across all repositories
- Identify shared dependencies that can be migrated together
- Find projects still using deprecated tooling
Due Diligence
For acquisitions or audits:
- Generate complete technology inventory
- Assess alignment with organization standards
- Identify licensing implications
Example Output
{
"toolingInventory": {
"frontend": {
"framework": "react",
"version": "18.2.0",
"stateManagement": ["zustand"],
"styling": ["tailwindcss", "@tailwindcss/forms"]
},
"metaFramework": {
"name": "next",
"version": "14.1.0"
},
"bundler": {
"name": "turbopack",
"notes": "Via Next.js built-in"
},
"backend": {
"framework": null,
"api": ["@trpc/server", "@trpc/next"]
},
"orm": {
"name": "prisma",
"version": "5.8.1"
},
"testing": {
"runner": "vitest",
"e2e": "playwright",
"utilities": ["@testing-library/react", "msw"]
},
"observability": {
"errorTracking": "@sentry/nextjs",
"logging": "pino"
},
"validation": ["zod"],
"ci": ["github-actions"]
}
}