@yuants/vendor-binance

npm

Is @yuants/vendor-binance safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @yuants/vendor-binance v0.14.7. Trust score: 60/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)

@yuants/vendor-binance 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.

@yuants/vendor-binance Capabilities & Permissions

What @yuants/vendor-binance 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.

ACCESS_KEYOPEN_INTEREST_TTLPUBLIC_ONLYSECRET_KEYUSE_HTTP_PROXYWRITE_QUOTE_TO_SQL

AGENTS.md for @yuants/vendor-binance

Good instructions lead to good results. brin adds @yuants/vendor-binance 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 →

@yuants/vendor-binance Documentation & Source Code

For the full @yuants/vendor-binance README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @yuants/vendor-binance safety

Weekly Downloads

73

Version

0.14.7

Last Scanned

5 hours ago

Trust Score

60/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: ACCESS_KEY, OPEN_INTEREST_TTL, PUBLIC_ONLY...

Is @yuants/vendor-binance Safe? | npm Safety Scan - brin