@vercel/node
32.0.0 · 18 Nov 2026Apache-2.06.3M / weekRepositoryHomepagenpmAtom feed
Your version
Security advisories
From OSV, open ones first. Each release line gets its own fix: an older major is fixed by a patch on that major, not by moving to the newest one.
No known security advisory for @vercel/node.
Quality and security signals
What npm and deps.dev say about the latest release. Signals, not a verdict.
- Licence
- ProvenanceNo provenance statement on 31.0.0Says where the release was built and from which commit. It does not say the code is safe.
- Published byGitHub Actions
- Maintainers on npm
- Size
- GitHub stars16,600 on vercel/vercel
- Last release31.0.0, 13 November 2026
- OpenSSF Scorecard6.1 / 10 · 24 Aug 2026Lowest: CII-Best-Practices 0, Fuzzing 0, SAST 0, Token-Permissions 0Grades the repository's practices (reviews, CI, branch protection), not the package's code.
Reading releases, release notes and advisories…
Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.