brin
brin

tsconfig-paths

npm

Is tsconfig-paths safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for tsconfig-paths v4.2.0. Trust score: 85/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)

tsconfig-paths 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.

tsconfig-paths Capabilities & Permissions

What tsconfig-paths can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

.env (r)package.json (r)package.json (r)package.json (r)node_modules (r)package.json (r)package.json (r)package.json (r)+13 more

AGENTS.md for tsconfig-paths

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

tsconfig-paths Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about tsconfig-paths safety

Weekly Downloads

57.1M

Version

4.2.0

License

MIT

Last Scanned

Jan 31, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is tsconfig-paths Safe? | npm Safety Scan - brin