brin
brin

@hapi/validate

npm

Is @hapi/validate safe to use?

The latest brin safety scan flagged @hapi/validate v2.0.1 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 85/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

@hapi/validate Has Warnings

Warnings detected due to potential concerns

warning
CVEs

0

Threats

0

Install Scripts

0

Risk Indicators

  • •Can spawn child processes

brin Recommendations

  • →This package has warnings detected. Evaluate the specific concerns before proceeding.

Install with brin add @hapi/validate to automatically apply these checks before installation.

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.

@hapi/validate Capabilities & Permissions

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

Process Spawning

This package can spawn child processes.

AGENTS.md for @hapi/validate

Good instructions lead to good results. brin adds @hapi/validate 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 →

@hapi/validate Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about @hapi/validate safety

Weekly Downloads

1.6M

Version

2.0.1

License

BSD-3-Clause

Last Scanned

Feb 1, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is @hapi/validate Safe? | npm Safety Scan - brin