← Sato Check
Sato Check · Package
@jup-ag/api
npm:@jup-ag/api · v6.0.48 · sha256:b7ad81c4d684 · as of 2026-09-26
- Does it take your key? declared
- It asks for a private key or seed phrase in its setup.
- The project says so — README, config, env list or tool description.
- 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? no evidence
- First profile of this subject — nothing to compare yet.
- No evidence line on file for this question yet.
Is this your project? Respond →Dispute this reading
Hosts contacted
| Host | When | Role | Evidence |
|---|---|---|---|
| api.jup.ag | code | vendor | traced |
| lite-api.jup.ag | code | vendor | traced |
Evidence (3 lines)
- tracedT-hosts2026-09-26
api.jup.ag appears in shipped code (vendor).
dist/index.js
- tracedT-hosts2026-09-26
lite-api.jup.ag appears in shipped code (vendor).
dist/index.js
- declaredD-env-key2026-09-26
Setup names PRIVATE_KEY as something to provide.
deploy_spec.requires
Limits
- The observed lane has not run on this version: not yet run on this version
- Traced analysis follows flows inside one module only; a key handed from one module to another 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-1
Maintain this project? Respond to this reading
Loading sign-in…