Package

almanak

pypi:almanak · v3.1.1 · sha256:b2322a0d3ce7 · as of 2026-11-05

Does it take your key?: No private-key read found in what we read of its setup and published code — the limits say how much that was.; The project says so — README, config, env list or tool description.
Does your key leave?: 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?: Unknown — we could not read what it exposes.; No evidence line on file for this question yet.
What changed?: No change in key, host or fund behaviour since 3.1.0.; Our static read of the published artifact found it.

Hosts contacted

Host	When	Role	Evidence
captured-gateway.invalid	code	other	traced
docs.morpho.org	code	other	traced

Evidence (3 lines)

tracedT-hosts2026-11-05
captured-gateway.invalid appears in shipped code (other).
src/almanak/backtest/pool_reads.py
tracedT-hosts2026-11-05
docs.morpho.org appears in shipped code (other).
src/almanak/connectors/lending_rates.py
declaredD-doc-custody2026-11-05
The project's own text describes its custody model: "Non-custodial design ensures users maintain full control of funds"
https://raw.githubusercontent.com/almanak-co/sdk/HEAD/README.md (line 416)

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: Python read line by line, not parsed; 1183 code files; read 400, entry points first.

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…