You Cannot Upgrade What You Do Not Know About
Ask an engineer what technologies their project uses and you will get a confident answer: "React, Node, PostgreSQL, Stripe." Ask them to list every framework, library, build tool, testing framework, and cloud SDK — and the confidence fades.
In modern codebases, the technology stack is far larger than what fits in anyone's head. A typical project might use dozens of tools across categories that no single engineer fully tracks.
Vibgrate's Tooling Inventory and Service Dependencies scanners automate this discovery.
Tooling Inventory
The Tooling Inventory scanner maps your full technology stack by detecting package names across your dependency manifests. It categorises them into:
| Category | Examples |
|---|---|
| Frontend | React, Vue, Angular, Svelte, Solid |
| Meta-frameworks | Next.js, Nuxt, Astro, Remix |
| Bundlers | Vite, webpack, esbuild, Rollup |
| Backend | Express, Fastify, NestJS, Hono |
| ORM / DB | Prisma, Drizzle, TypeORM, EF Core |
| Testing | Vitest, Jest, Playwright, xUnit |
| Observability | Sentry, OpenTelemetry, Pino, Winston |
This is not just a list — it is a categorised, version-aware inventory that tells you what you have and how current it is. Combined with the drift score, you can see at a glance: "We use Vite 4.x, but 6.x is current" or "Our testing stack is fully up to date."
Service Dependencies
The Service Dependencies scanner goes further, mapping external services and platform dependencies by detecting SDK packages:
| Category | Examples |
|---|---|
| Payment | Stripe, Braintree, PayPal |
| Auth | Auth0, Clerk, Firebase, Passport |
| Cloud SDKs | AWS SDK, Azure SDK, Google Cloud |
| Databases | PostgreSQL (pg), MongoDB, Redis |
| Messaging | SQS, SNS, Kafka, BullMQ |
| Observability | Sentry, DataDog, New Relic |
This mapping reveals your integration surface — every external service that your code talks to, discovered automatically from your dependency graph.
Why This Matters
For Migration Planning
When migrating between cloud providers, you need to know every AWS SDK call in your codebase. When switching auth providers, you need to know everywhere Passport is used. The Service Dependencies scanner gives you this map without manual code review.
For Risk Assessment
A service dependency is a contract. If the Stripe SDK is three major versions behind, your payment integration may be using deprecated API endpoints that Stripe could remove. Service dependency drift is as important as framework drift.
For Onboarding
New team members get a complete picture of the technology stack from the scan output instead of piecing it together from tribal knowledge and README files that may be outdated.
For Architecture Reviews
Combined with the Architecture Layer Mapping scanner, you can see service dependencies per layer: "The data access layer depends on PostgreSQL and Redis. The infrastructure layer depends on AWS SQS and Auth0." This is precisely the information architecture reviews need.
Build and Deploy Surface Area
As a companion to tooling and service discovery, the Build & Deploy Surface Area scanner detects your CI/CD and infrastructure setup:
- CI systems: GitHub Actions, GitLab CI, Azure DevOps, Jenkins, CircleCI
- Containerisation: Docker, Docker Compose
- IaC: Terraform, Bicep, CloudFormation, Pulumi
- Release tooling: Changesets, semantic-release, GitVersion
- Package managers and monorepo tools
Together, these three scanners produce a complete map of what your project is built with, what it talks to, and how it is deployed.
The Vibgrate Drift Intelligence Engine automates this discovery because manual technology inventories are always incomplete and always out of date. A scan that runs in CI keeps the inventory current — automatically.
Map your full stack. Sign up at dash.vibgrate.com to discover every tool, service, and integration in your codebase — and see which ones have drifted.