get-source

npm

Is get-source safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for get-source v2.0.12. 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)

get-source 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.

get-source Capabilities & Permissions

What get-source 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.

bar.combar.js.mapfoo.comgoogle.com
Protocols: http, https

Filesystem Access

Reads from the filesystem.

package.json (r)

AGENTS.md for get-source

Good instructions lead to good results. brin adds get-source 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 →

get-source Documentation & Source Code

For the full get-source README, API documentation, and source code, visit the official package registry.

Frequently asked questions about get-source safety

Weekly Downloads

1.8M

Version

2.0.12

License

Unlicense

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: bar.com, bar.js.map, foo.com...

Filesystem

Reads files

Is get-source Safe? | npm Safety Scan - brin