@peaqos/peaq-os-sdk
npm:@peaqos/peaq-os-sdk · v0.12.0 · sha256:42e1d167846f · as of 2026-10-24
- 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? declared
- Unknown — we could not read what it exposes.
- The project says so — README, config, env list or tool description.
- What changed? no evidence
- No change in key, host or fund behaviour since 0.11.2.
- No evidence line on file for this question yet.
Is this your project? Respond →Dispute this reading
Evidence (3 lines)
- declaredD-env-key2026-10-24
Setup names PEAQOS_PRIVATE_KEY as something to provide.
deploy_spec.requires
- declaredD-env-key2026-10-24
Setup names PRIVATE_KEY as something to provide.
@peaqos/peaq-os-sdk@0.12.0/README.md
- declaredD-doc-funds2026-10-24
The project's own text says it carries out transactions: "The suites under tests/integration/ are gated on their own environment variables, listed in each suite's header; several submit real transactions. A local .env that sets them arms those writes on a plain pnpm test, so u…"
@peaqos/peaq-os-sdk@0.12.0/README.md (line 338)
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.
- Traced: dist/index.cjs skipped (over 2 MB); dist/index.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-3
Maintain this project? Respond to this reading
Loading sign-in…