oauth4webapi

npm

Is oauth4webapi safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for oauth4webapi v3.8.4. 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)

oauth4webapi 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.

oauth4webapi Capabilities & Permissions

What oauth4webapi 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.

as.example.comclient.example.comdatatracker.ietf.orgdeveloper.mozilla.orggithub.comopenid.netundici.nodejs.orgwww.iana.orgwww.rfc-editor.org
Protocols: https

AGENTS.md for oauth4webapi

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

oauth4webapi Documentation & Source Code

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

Frequently asked questions about oauth4webapi safety

Weekly Downloads

4.3M

Version

3.8.4

License

MIT

Other Versions

Last Scanned

Feb 7, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: as.example.com, client.example.com, datatracker.ietf.org...

Is oauth4webapi Safe? | npm Safety Scan - brin