matchers

npm

Is matchers safe to use?

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

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

matchers Capabilities & Permissions

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

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

matchers Documentation & Source Code

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

Frequently asked questions about matchers safety

Weekly Downloads

4

Version

0.0.1

Last Scanned

4 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

No special capabilities detected

Is matchers Safe? | npm Safety Scan - brin