express-api-error

npm

Is express-api-error safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for express-api-error v1.0.8. Trust score: 50/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)

express-api-error 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.

express-api-error Capabilities & Permissions

What express-api-error 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.

Environment Variables

Accesses the following environment variables.

NODE_ENV

AGENTS.md for express-api-error

Good instructions lead to good results. brin adds express-api-error 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 →

express-api-error Documentation & Source Code

For the full express-api-error README, API documentation, and source code, visit the official package registry.

Frequently asked questions about express-api-error safety

Weekly Downloads

10

Version

1.0.8

License

ISC

Last Scanned

4 hours ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Environment

Accesses: NODE_ENV

Is express-api-error Safe? | npm Safety Scan - brin