brin
brin

@contrast/escodegen

npm

Is @contrast/escodegen safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @contrast/escodegen v1.16.0. Trust score: 85/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)

@contrast/escodegen 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.

@contrast/escodegen Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

/usr/ (r)/usr/ (r)package.json (r)

AGENTS.md for @contrast/escodegen

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

@contrast/escodegen Documentation & Source Code

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

View on npmView Source

Frequently asked questions about @contrast/escodegen safety

Weekly Downloads

65

Version

1.16.0

License

BSD-2-Clause

Last Scanned

2 hours ago

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is @contrast/escodegen Safe? | npm Safety Scan - brin