brickken-cli
npm:brickken-cli · v0.4.13 · sha256:87bfdcf99486 · as of 2026-11-10
- Does it take your key? traced
- Yes — it reads private-key material. Local signing is what a wallet does; question 2 says whether the key leaves.
- Our static read of the published artifact found it.
- 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
- 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.brickken.com | code | vendor | traced |
| api.sandbox.brickken.com | code | vendor | traced |
| d4aqanatl1.execute-api.eu-west-1.amazonaws.com | code | other | traced |
| ethereum-sepolia-rpc.publicnode.com | code | rpc | traced |
Evidence (13 lines)
- tracedT-key-read2026-11-10
Reads process.env.BRICKKEN_PRIVATE_KEY.
dist/cli-config.js:48
- tracedT-key-read2026-11-10
Reads process.env.BKN_PRIVATE_KEY.
dist/cli-config.js:48
- tracedT-key-read2026-11-10
Reads process.env.BRICKKEN_PRIVATE_KEY.
dist/internal/core/config.js:59
- tracedT-key-read2026-11-10
Reads process.env.BKN_PRIVATE_KEY.
dist/internal/core/config.js:59
- tracedT-hosts2026-11-10
api.brickken.com appears in shipped code (vendor).
dist/internal/core/config.js
- tracedT-hosts2026-11-10
api.sandbox.brickken.com appears in shipped code (vendor).
dist/internal/core/config.js
- tracedT-hosts2026-11-10
d4aqanatl1.execute-api.eu-west-1.amazonaws.com appears in shipped code (other).
dist/internal/core/config.js
- tracedT-hosts2026-11-10
ethereum-sepolia-rpc.publicnode.com appears in shipped code (rpc).
dist/internal/core/receipts.js
- tracedT-key-named2026-11-10
The shipped code names BRICKKEN_PRIVATE_KEY in a message to the user.
dist/commands/rams.js
- tracedT-key-named2026-11-10
The shipped code names BKN_PRIVATE_KEY in a message to the user.
dist/commands/rams.js
- declaredD-env-key2026-11-10
Setup names BRICKKEN_PRIVATE_KEY as something to provide.
deploy_spec.requires
- declaredD-env-key2026-11-10
Setup names BKN_PRIVATE_KEY as something to provide.
brickken-cli@0.4.13/README.md
- declaredD-doc-funds2026-11-10
The project's own text says it carries out transactions: "3. sends the signed payload to /send-transactions"
brickken-cli@0.4.13/README.md (line 504)
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…