oauth-1.0a
npmIs oauth-1.0a safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for oauth-1.0a v2.2.6. 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)
oauth-1.0a Passed Security Checks
No security concerns detected
0
0
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.
oauth-1.0a Capabilities & Permissions
What oauth-1.0a can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Environment Variables
Accesses the following environment variables.
AGENTS.md for oauth-1.0a
Good instructions lead to good results. brin adds oauth-1.0a documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
oauth-1.0a Documentation & Source Code
For the full oauth-1.0a README, API documentation, and source code, visit the official package registry.
Frequently asked questions about oauth-1.0a safety
Install (safety-checked)
Weekly Downloads
Version
2.2.6License
MITLast Scanned
Trust Score
Capabilities
Accesses: BITBUCKET_CONSUMER_PUBLIC, BITBUCKET_CONSUMER_SECRET, FLICKR_CONSUMER_SECRET...