@acrool/window-launcher

npm

Is @acrool/window-launcher safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @acrool/window-launcher v2.0.6. Trust score: 75/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)

@acrool/window-launcher 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.

@acrool/window-launcher Capabilities & Permissions

No system capabilities detected for @acrool/window-launcher. It does not appear to access the network, filesystem, spawn processes, or use native modules. No capability concerns identified for use with AI coding agents.

AGENTS.md for @acrool/window-launcher

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

@acrool/window-launcher Documentation & Source Code

For the full @acrool/window-launcher README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @acrool/window-launcher safety

Weekly Downloads

45

Version

2.0.6

License

MIT

Last Scanned

3 hours ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

No special capabilities detected

Is @acrool/window-launcher Safe? | npm Safety Scan - brin