ccxt-typescript
Build CCXT Exchange Integrations in TypeScript
Exchange integrations require different methods for market data, authentication, and trading. This skill provides CCXT examples and reference guidance for TypeScript and JavaScript projects.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "ccxt-typescript" from https://skillstore.io/skills/ccxt-ccxt-typescript.md and its manifest at https://skillstore.io/api/skills/ccxt-ccxt-typescript/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "ccxt-typescript". How should I choose between REST and WebSocket methods for a live price dashboard?
Expected outcome:
- Use REST to load market metadata and retrieve an initial ticker.
- Use watchTicker or watchOrderBook for ongoing updates after checking exchange support.
- Handle connection errors and close the exchange connection during shutdown.
Using "ccxt-typescript". What should I check before using a router plan for real orders?
Expected outcome:
- Keep execution in dry-run mode while validating symbols, amounts, precision, and market limits.
- Set a stable execution identity, a notional cap, quote-asset USD rates, and a maximum plan age.
- Review uncertain outcomes against venue orders before retrying; the documented identity guard does not survive restarts.
Using "ccxt-typescript". How should I configure private CCXT access?
Expected outcome:
- Read the exchange key and secret from environment variables on the server.
- Grant only the permissions required by the workflow and enable rate limiting.
- Avoid exposing secrets or complete authenticated responses through logs or browser code.
Security Audit
Low RiskMost static alerts are false positives caused by Markdown backticks, placeholder credentials, documented proxy settings, and exchange API terminology. Two browser examples load mutable CDN scripts, and diagnostic examples lack safeguards for sensitive response logging. No evidence found of prompt injection, credential exfiltration, or malicious command execution in the reviewed file.
Confirmed security concerns (1)
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (50)
๐ Network access (18)
๐ Env variables (11)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/ccxt-ccxt-typescript/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/ccxt-ccxt-typescript?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/ccxt-ccxt-typescript?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/ccxt-ccxt-typescript/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/ccxt-ccxt-typescript.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
ccxt. (2026). ccxt-typescript security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/ccxt-ccxt-typescript/audits/1BibTeX citation
@techreport{ccxt-ccxt-ccxt-typescript-2026,
author = {ccxt},
title = {ccxt-typescript security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/ccxt-ccxt-typescript/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ccxt-typescript security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "ccxt"
date-released: "2026-11-15"
url: "https://skillstore.io/skills/ccxt-ccxt-typescript/audits/1"
identifiers:
- type: other
value: "skillstore:ccxt-ccxt-typescript:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Connect a Market Data Dashboard
Choose REST queries or WebSocket streams for tickers and order books, with capability checks and connection cleanup.
Integrate Account and Order Workflows
Plan authenticated balance queries and order management with environment variables, rate limits, and exchange error handling.
Review Multi-Venue Execution Safety
Assess router plans using dry runs, stable execution identities, notional caps, freshness limits, and uncertain-outcome handling.
Try These Prompts
Show a TypeScript CCXT example that loads Binance markets and fetches the BTC/USDT ticker without credentials. Explain the returned price fields.
Create a TypeScript ccxt.pro order book stream for BTC/USDT. Include capability checks, error handling, cancellation, and connection cleanup.
Design a Node.js CCXT balance integration using environment credentials and minimal permissions. Include rate limiting and redacted errors; do not place orders.
Review my CCXT router plan for stable idempotency, notional caps, price freshness, and unknown outcomes. Propose a dry-run validation checklist without executing trades.
Best Practices
- Check exchange capabilities and loaded market constraints before selecting methods or constructing orders.
- Use minimal credential permissions, redact private logs, and pin reviewed dependency versions.
- Validate trading workflows with dry runs; configure execution caps, freshness limits, and stable identities before explicitly authorizing live orders.
Avoid
- Copying authenticated examples into browser code or storing real exchange secrets in source control.
- Retrying an uncertain order submission without checking whether the venue already accepted it.
- Assuming every exchange supports every listed method or that REST requests guarantee trade execution.