@epilot/validators

npm

Is @epilot/validators safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @epilot/validators v0.0.22. 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)

@epilot/validators 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.

@epilot/validators Capabilities & Permissions

What @epilot/validators 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.

NODE_ENV

AGENTS.md for @epilot/validators

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

@epilot/validators Documentation & Source Code

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

Frequently asked questions about @epilot/validators safety

Weekly Downloads

522

Version

0.0.22

License

MIT

Last Scanned

3 days ago

Trust Score

70/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: NODE_ENV

Is @epilot/validators Safe? | npm Safety Scan - brin