w3xed

npm

Is w3xed safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for w3xed v1.0.0-beta16. Trust score: 60/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)

w3xed 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.

w3xed Capabilities & Permissions

What w3xed 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)package.json (r)

Process Spawning

This package can spawn child processes.

AGENTS.md for w3xed

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

w3xed Documentation & Source Code

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

Frequently asked questions about w3xed safety

Weekly Downloads

12

Version

1.0.0-beta16

License

ISC

Last Scanned

3 hours ago

Trust Score

60/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Process

Spawns child processes

Is w3xed Safe? | npm Safety Scan - brin