@vercel/nft
[](https://github.com/vercel/nft/actions/workflows/ci.yml)
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from vercel-release-bot to GitHub Actions is a routine CI change within the Vercel org. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() is used inside a Proxy handler for module resolution interception — standard pattern for a module tracing tool, not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Vercel org regularly updates maintainer roster as team grows; new maintainers are recognizable Vercel employees. No code changes accompany the roster update. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers appear to be former Vercel staff; consistent with normal org churn. No suspicious code changes. | ai | |
| phantom-deps | phantom-dep:mkdirp | AI (phantom-deps): mkdirp is declared and used in config; phantom-dep pattern is stable for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): picomatch is a well-known, widely-used glob library and is actually the engine underlying micromatch; this swap is a legitimate dependency simplification for this package. | ai | |
| dependencies | unvetted-dep:node-gyp-build | AI (dependencies): node-gyp-build is a standard native addon utility; its use in @vercel/nft for resolving native binary paths is expected and stable across versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is core to nft's dependency-tracing functionality; it resolves node-gyp-build paths for native bindings analysis. Stable pattern across versions. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval('require.resolve(...)') is a known bundler-safe pattern for module resolution in static analysis tools; not an attack vector in this context. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.9.0 | 12 / 102 | |
| 1.4.0 | 12 / 102 | |
| 1.0.0 | 12 / 102 | |
| 0.29.3 | 12 / 104 | |
| 0.29.0 | 12 / 104 | |
| 0.28.0 | 12 / 104 | |
| 0.27.4 | 12 / 103 | |
| 0.22.6 | 11 / 99 | |
| 0.22.1 | 11 / 99 | |
| 0.17.3 | 11 / 94 | |
| 0.16.0 | 15 / 92 | |
| 0.9.3 | 16 / 84 | |
| 0.9.2 | 16 / 84 |
v1.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.