wait.for

npm

Is wait.for safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for wait.for v0.6.6. Trust score: 65/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)

wait.for 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.

wait.for Capabilities & Permissions

What wait.for can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

AGENTS.md for wait.for

Good instructions lead to good results. brin adds wait.for 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 →

wait.for Documentation & Source Code

For the full wait.for README, API documentation, and source code, visit the official package registry.

Frequently asked questions about wait.for safety

Weekly Downloads

79

Version

0.6.6

License

Creative Commons, MIT

Last Scanned

4 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is wait.for Safe? | npm Safety Scan - brin