Sato Check · Package
skills
npm:skills · v1.7.0 · sha256:8d1466f792ba · 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 |
|---|---|---|---|
| add-skill.vercel.sh | code | other | traced |
| api.github.com | code | registry | traced |
| connectors-skills.zapier.com | code | other | traced |
| developers.notion.com | code | other | traced |
| github.com | code | registry | traced |
| gitlab.com | code | other | traced |
| notion.so | code | other | traced |
| raw.githubusercontent.com | code | registry | traced |
| schemas.agentskills.io | code | other | traced |
| skills.sh | code | other | traced |
| registry.npmjs.org | install | registry | observed |
Evidence (11 lines)
- observedO-hosts2026-09-25
registry.npmjs.org was contacted during install (registry).
sandbox:obs_f1c78c0e5e6837d4
- tracedT-hosts2026-09-26
add-skill.vercel.sh appears in shipped code (other).
dist/cli.mjs
- tracedT-hosts2026-09-26
api.github.com appears in shipped code (registry).
dist/cli.mjs
- tracedT-hosts2026-09-26
connectors-skills.zapier.com appears in shipped code (other).
dist/cli.mjs
- tracedT-hosts2026-09-26
developers.notion.com appears in shipped code (other).
dist/cli.mjs
- tracedT-hosts2026-09-26
github.com appears in shipped code (registry).
dist/cli.mjs
- tracedT-hosts2026-09-26
gitlab.com appears in shipped code (other).
dist/cli.mjs
- tracedT-hosts2026-09-26
notion.so appears in shipped code (other).
dist/cli.mjs
- tracedT-hosts2026-09-26
raw.githubusercontent.com appears in shipped code (registry).
dist/cli.mjs
- tracedT-hosts2026-09-26
schemas.agentskills.io appears in shipped code (other).
dist/cli.mjs
- tracedT-hosts2026-09-26
skills.sh appears in shipped code (other).
dist/cli.mjs
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..
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…