open-with-me

npm

Is open-with-me safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for open-with-me v0.6.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)

open-with-me Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

1

Install Scripts Detected

install

This package runs scripts during installation. Review these scripts before installing.

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.

open-with-me Capabilities & Permissions

What open-with-me 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.

npm

AGENTS.md for open-with-me

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

open-with-me Documentation & Source Code

For the full open-with-me README, API documentation, and source code, visit the official package registry.

Frequently asked questions about open-with-me safety

Weekly Downloads

13

Version

0.6.0

License

MIT

Last Scanned

2 days ago

Trust Score

65/100·Legitimacy signals, not safety

Install Scripts

This package has install scripts that run automatically:

install

Capabilities

Process

Spawns child processes

Is open-with-me Safe? | npm Safety Scan - brin