@vercel/nestjs

npm

Is @vercel/nestjs safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @vercel/nestjs v0.2.38. Trust score: 70/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

@vercel/nestjs Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

@vercel/nestjs Capabilities & Permissions

What @vercel/nestjs can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Environment Variables

Accesses the following environment variables.

EXPERIMENTAL_NODE_TYPESCRIPT_ERRORS

AGENTS.md for @vercel/nestjs

Good instructions lead to good results. brin adds @vercel/nestjs documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

@vercel/nestjs Documentation & Source Code

For the full @vercel/nestjs README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @vercel/nestjs safety

Weekly Downloads

1.0M

Version

0.2.38

License

Apache-2.0

Other Versions

Last Scanned

Feb 10, 2026

Trust Score

70/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: EXPERIMENTAL_NODE_TYPESCRIPT_ERRORS

Is @vercel/nestjs Safe? | npm Safety Scan - brin