@hpcc-js/map

npm

Is @hpcc-js/map safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @hpcc-js/map v3.4.11. 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)

@hpcc-js/map 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.

@hpcc-js/map Capabilities & Permissions

What @hpcc-js/map 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.

api.mapbox.comavinmathew.comcreativecommons.orgdevelopers.google.comgithub.comhunch.seleafletjs.commaps.googleapis.compurl.orgrsms.me+6 more
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for @hpcc-js/map

Good instructions lead to good results. brin adds @hpcc-js/map 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 →

@hpcc-js/map Documentation & Source Code

For the full @hpcc-js/map README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @hpcc-js/map safety

Weekly Downloads

2.1K

Version

3.4.11

License

Apache-2.0

Last Scanned

16 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: api.mapbox.com, avinmathew.com, creativecommons.org...

Process

Spawns child processes