Please report a vulnerability privately through GitHub's private reporting rather than in a public issue. I aim to answer within a few days.
- It reads
DEXPAPRIKA_API_KEYfrom the environment and hands it to the officialdexpaprika-sdk, which sends it only in theAuthorizationheader. - Requests go only to
https://api.dexpaprika.comorhttps://api-pro.dexpaprika.com. Any otherDEXPAPRIKA_BASE_URLis refused before a request is made, and redirects are not followed. - Every request has a timeout, and a rate limit is retried once at most.
- The key is never printed, logged or stored.
.envis in.gitignore.
Token symbols come from on-chain metadata that anyone can set. pool-depth strips control characters and bidirectional overrides from every string it gets from the API, in the text output and in the JSON.
One runtime dependency, dexpaprika-sdk, installed from a requirements file pinned with
hashes. CI actions are pinned to commit SHAs, Dependabot keeps both current, and the
workflow token is read-only.
For problems in the DexPaprika API itself, see https://docs.dexpaprika.com.