@basemaps/cli-vector

npm

Is @basemaps/cli-vector safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @basemaps/cli-vector v8.10.7. 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)

@basemaps/cli-vector 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.

@basemaps/cli-vector Capabilities & Permissions

What @basemaps/cli-vector can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Writes to the filesystem.

/tmp/ (r)/tmp/ (r)

AGENTS.md for @basemaps/cli-vector

Good instructions lead to good results. brin adds @basemaps/cli-vector 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 →

@basemaps/cli-vector Documentation & Source Code

For the full @basemaps/cli-vector README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @basemaps/cli-vector safety

Weekly Downloads

155

Version

8.10.7

License

MIT

Last Scanned

2 hours ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Filesystem

Writes files

Is @basemaps/cli-vector Safe? | npm Safety Scan - brin