@blackglory/match
npmIs @blackglory/match safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @blackglory/match v0.4.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)
@blackglory/match Passed Security Checks
No security concerns detected
0
0
1
Install Scripts Detected
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.
@blackglory/match Capabilities & Permissions
No system capabilities detected for @blackglory/match. 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 @blackglory/match
Good instructions lead to good results. brin adds @blackglory/match documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
@blackglory/match Documentation & Source Code
For the full @blackglory/match README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @blackglory/match safety
Install (safety-checked)
Weekly Downloads
Version
0.4.1License
MITLast Scanned
Trust Score
Install Scripts
This package has install scripts that run automatically:
prepare
Capabilities
No special capabilities detected