@picryl/geocoder
npmIs @picryl/geocoder safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @picryl/geocoder v0.2.4. 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)
@picryl/geocoder 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.
@picryl/geocoder Capabilities & Permissions
What @picryl/geocoder can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Network Access
This package makes network requests.
AGENTS.md for @picryl/geocoder
Good instructions lead to good results. brin adds @picryl/geocoder 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 →
@picryl/geocoder Documentation & Source Code
For the full @picryl/geocoder README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @picryl/geocoder safety
Install (safety-checked)
Weekly Downloads
Version
0.2.4License
Apachev2Last Scanned
Trust Score
Capabilities
Connects to: api.geonames.org, developer.yahoo.com, developers.google.com...