Skip to main content
Scanners

Tooling Inventory Scanner

Map your full technology stack by detecting packages across categories.

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

CategoryDetected Packages
React ecosystemreact, react-dom, @tanstack/react-query, zustand, jotai
Vue ecosystemvue, pinia, @vue/...
Angular@angular/core, @angular/cli
Sveltesvelte, @sveltejs/kit
Solidsolid-js, solid-start
CSStailwindcss, styled-components, @emotion/...

Meta-Frameworks

FrameworkDetected Packages
Next.jsnext
Nuxtnuxt
Astroastro
Remix@remix-run/...
SvelteKit@sveltejs/kit
Gatsbygatsby

Build Tools

CategoryDetected Packages
Bundlersvite, webpack, esbuild, rollup, parcel
Transpilerstypescript, @babel/core, swc
Task runnersturbo, nx, lerna, gulp

Backend

CategoryDetected Packages
HTTP frameworksexpress, fastify, hono, koa
Full frameworks@nestjs/core, adonisjs
API@trpc/server, graphql, @apollo/server
Serverlessserverless, sst, @aws-sdk/...

Data & ORM

CategoryDetected Packages
ORM/Query buildersprisma, drizzle-orm, typeorm, sequelize, knex
Database clientspg, mysql2, mongodb, redis
Validationzod, yup, joi, valibot

Testing

CategoryDetected Packages
Test runnersvitest, jest, mocha, ava
E2Eplaywright, cypress, puppeteer
Utilities@testing-library/..., msw, supertest

Observability

CategoryDetected Packages
Error tracking@sentry/node, @sentry/react
Monitoringdd-trace, newrelic
Loggingpino, 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:

  1. Audit current tooling across all repositories
  2. Identify shared dependencies that can be migrated together
  3. 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"]
  }
}

Related Documentation