cls-hooked

npm

Is cls-hooked safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for cls-hooked v4.2.2. 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)

cls-hooked 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.

cls-hooked Capabilities & Permissions

What cls-hooked 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.

DEBUGDEBUG_CLS_HOOKED

AGENTS.md for cls-hooked

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

cls-hooked Documentation & Source Code

For the full cls-hooked README, API documentation, and source code, visit the official package registry.

Frequently asked questions about cls-hooked safety

Weekly Downloads

3.0M

Version

4.2.2

License

BSD-2-Clause

Last Scanned

Jan 31, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: DEBUG, DEBUG_CLS_HOOKED

Is cls-hooked Safe? | npm Safety Scan - brin