strangler

npm

Is strangler safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for strangler v2.1.0. Trust score: 55/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)

strangler Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

1

Install Scripts Detected

prepare

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.

strangler Capabilities & Permissions

No system capabilities detected for strangler. 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 strangler

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

strangler Documentation & Source Code

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

Frequently asked questions about strangler safety

Weekly Downloads

849

Version

2.1.0

License

MIT

Last Scanned

2 days ago

Trust Score

55/100·Legitimacy signals, not safety

Install Scripts

This package has install scripts that run automatically:

prepare

Capabilities

No special capabilities detected

Is strangler Safe? | npm Safety Scan - brin