@run-z/exec-z

npm

Is @run-z/exec-z safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @run-z/exec-z v2.0.0. 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)

@run-z/exec-z 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.

@run-z/exec-z Capabilities & Permissions

What @run-z/exec-z 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.

AGENTS.md for @run-z/exec-z

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

@run-z/exec-z Documentation & Source Code

For the full @run-z/exec-z README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @run-z/exec-z safety

Weekly Downloads

31

Version

2.0.0

License

MIT

Last Scanned

3 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is @run-z/exec-z Safe? | npm Safety Scan - brin