# vercel/nft

Node.js dependency tracing utility

Repository: https://github.com/vercel/nft
Canonical: https://ross.abutalabs.com/products/nft
Homepage: https://npmjs.com/@vercel/nft
Language: JavaScript
License: MIT
License Family: permissive
Topics: static-analysis
Last push: 2026-08-18T16:43:08+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 98, release rhythm 98, longevity 100
- inputs: {"age_days": 2616, "days_push": 15, "days_rel": 15, "gap_med": 18.0, "n_releases_24m": 31}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1669, forks 182 (observed 2026-08-28T04:05:19.908225+00:00)

## What it is
Node File Trace (@vercel/nft) is a Node.js library that statically analyzes application entry files to determine exactly which files, node_modules packages, and assets are needed at runtime. It provides the tracing engine used by Vercel and @vercel/ncc to produce minimal file lists for deployment without bundling.

## Use cases
- trace which node_modules files are actually required at runtime
- generate a minimal file list for deploying a Node.js app to AWS Lambda
- package a Node.js serverless function without bundling
- tree-shake node_modules without webpack
- statically analyze require and import statements in a Node.js codebase
- find all assets and binaries a Node.js application depends on
- reduce deployment size by excluding unnecessary files

## When to choose
- You need to know the exact set of files required to run a Node.js application for deployment or packaging
- You want tree-shaking of node_modules without actually bundling or moving assets and binaries
- You need programmatic tracing with support for ESM exports/imports conditions, dynamic requires, and assets

## When to avoid
- You want a single bundled output file - use a bundler like webpack, esbuild, or @vercel/ncc instead
- Your project is not JavaScript/Node.js based
- You rely heavily on runtime-constructed require paths that static analysis cannot resolve

## Facets
- artifact type: library
- maturity: active
- function: developer-tools, parser, build-tool
- domain: developer-tools, backend, web-development
- platform: serverless
- tags: static-analysis, dependency-tracing, file-tracing, tree-shaking, node-modules, module-resolution, esm, serverless-packaging, vercel, automation, nodejs

## Member repositories
- vercel/nft (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:19.908225+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:42:48.103671+00:00, confidence not recorded.
  - readme: https://github.com/vercel/nft (fetched 2026-08-28T04:05:19.908225+00:00, sha 329e1b90e683)
- Data as of 2026-08-30T08:39:29.467469+00:00.