@nexajs/token

npm

Is @nexajs/token safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @nexajs/token v24.11.1. Trust score: 75/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)

@nexajs/token 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.

@nexajs/token Capabilities & Permissions

What @nexajs/token 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.

bitcoin.stackexchange.comspec.nexa.orgtokenapi.otoplo.com
Protocols: https

AGENTS.md for @nexajs/token

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

@nexajs/token Documentation & Source Code

For the full @nexajs/token README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @nexajs/token safety

Weekly Downloads

62

Version

24.11.1

License

MIT

Last Scanned

2 hours ago

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: bitcoin.stackexchange.com, spec.nexa.org, tokenapi.otoplo.com

Is @nexajs/token Safe? | npm Safety Scan - brin