← Sato Check
Sato Check · Package
use-agently
npm:use-agently · v0.35.0 · sha256:ad83e7fb949f · as of 2026-09-26
- 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? observed
- Not observed — no planted key left during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered.
- We ran it with planted test keys and saw it.
- 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 |
|---|---|---|---|
| registry.npmjs.org | install | registry | observed |
| api.use-agently.com | start | vendor | observed |
| registry.npmjs.org | start | registry | observed |
Evidence (3 lines)
- observedO-hosts2026-09-25
registry.npmjs.org was contacted during install (registry).
sandbox:obs_d3877393fbae2831
- observedO-hosts2026-09-25
api.use-agently.com was contacted during start (vendor).
sandbox:obs_d3877393fbae2831
- observedO-hosts2026-09-25
registry.npmjs.org was contacted during start (registry).
sandbox:obs_d3877393fbae2831
Limits
- Traced analysis follows flows inside one module only; a key handed from one module to another is not followed.
- Key egress not observed during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered.
- No tool inventory was available, so fund actions were not read.
- Sandbox: DNS queries made directly by the target are not logged; hosts are recorded from proxied HTTP(S) requests and CONNECTs..
- Sandbox: Code that ignores HTTP(S)_PROXY has no route out of the sandbox, so its attempts are not captured..
- Traced: build/bin.js skipped (over 2 MB).
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…