@privy-io/node
npm:@privy-io/node · v0.39.0 · sha256:f5a19e11cc91 · as of 2026-11-11
- Does it take your key? no evidence
- No private-key read found in what we read of its setup and published code — the limits say how much that was.
- No evidence line on file for this question yet.
- Does your key leave? no evidence
- Not yet run — we have not run this version with planted test keys.
- No evidence line on file for this question yet.
- Can it move funds on its own? no evidence
- Unknown — we could not read what it exposes.
- No evidence line on file for this question yet.
- What changed? traced
- No change in key, host or fund behaviour since 0.38.0.
- Our static read of the published artifact found it.
Is this your project? Respond →Dispute this reading
Hosts contacted
| Host | When | Role | Evidence |
|---|---|---|---|
| abs.twimg.com | code | other | traced |
| api.privy.io | code | vendor | traced |
| api.staging.privy.io | code | vendor | traced |
| pbs.twimg.com | code | other | traced |
Evidence (4 lines)
- tracedT-hosts2026-11-11
abs.twimg.com appears in shipped code (other).
lib/identity-token.js
- tracedT-hosts2026-11-11
api.privy.io appears in shipped code (vendor).
client.js
- tracedT-hosts2026-11-11
api.staging.privy.io appears in shipped code (vendor).
client.js
- tracedT-hosts2026-11-11
pbs.twimg.com appears in shipped code (other).
lib/identity-token.js
Limits
- The observed lane has not run on this version: not yet run on this version
- Traced analysis follows flows inside one module and one hop across a relative import; a longer chain is not followed.
- The observed lane has not run on this version.
- No tool inventory was available, so fund actions were not read.
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
sato.custody/v1 · custody-3
Maintain this project? Respond to this reading
Loading sign-in…