third-party-web

npm

Is third-party-web safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for third-party-web v0.29.0. 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)

third-party-web 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.

third-party-web Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

AGENTS.md for third-party-web

Good instructions lead to good results. brin adds third-party-web 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 →

third-party-web Documentation & Source Code

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

Frequently asked questions about third-party-web safety

Weekly Downloads

2.3M

Version

0.29.0

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is third-party-web Safe? | npm Safety Scan - brin