detect-nearest-browser-locale
npmIs detect-nearest-browser-locale safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for detect-nearest-browser-locale v19.0.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)
detect-nearest-browser-locale Passed Security Checks
No security concerns detected
0
0
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.
detect-nearest-browser-locale Capabilities & Permissions
No system capabilities detected for detect-nearest-browser-locale. 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 detect-nearest-browser-locale
Good instructions lead to good results. brin adds detect-nearest-browser-locale 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 →
detect-nearest-browser-locale Documentation & Source Code
For the full detect-nearest-browser-locale README, API documentation, and source code, visit the official package registry.
Frequently asked questions about detect-nearest-browser-locale safety
Install (safety-checked)
Weekly Downloads
Version
19.0.0License
MITLast Scanned
Trust Score
Capabilities
No special capabilities detected