ClawHub

Lineage Claws

v0.4.4

The trust gate for MO§ES™ governance. Cryptographic origin verification — every sovereign chain must trace to the filing anchor or it cannot reconstruct. The...

⭐ 0· 245·2 current·2 all-time
byburnmydays@sunrisesillneversee·duplicate of @sunrisesillneversee/claws
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
The skill's name/description match the included scripts and commands (init, verify, badge, check). It is a local lineage/anchor verifier and only needs Python and write access to ~/.openclaw. Minor metadata mismatches: SKILL.md declares python3 as a bin and lists stateDirs (~/.openclaw/*) while the registry summary earlier listed no required binaries or config paths — this is a bookkeeping inconsistency but not a functional mismatch.
✓
Instruction Scope
Runtime instructions and the two Python scripts operate on local files under ~/.openclaw (ledger, lineage, archival) and import the provided archival.py. They do not attempt to read unrelated system files, environment secrets, or call external endpoints; actions are within the described lineage verification scope.
✓
Install Mechanism
No install spec (instruction-only skill) and included code runs under Python. Nothing is downloaded from arbitrary URLs; files are packaged with the skill. This lowers install risk.
ℹ
Credentials
The skill requires no credentials or external tokens. It persists state in ~/.openclaw which is proportionate to a local lineage ledger. Note: SKILL.md metadata lists stateDirs; the registry metadata omitted them — verify expected file locations before installing.
ℹ
Persistence & Privilege
The skill writes persistent files (lineage.json, audit_ledger.jsonl, archival_chain.json) under the user's home (~/.openclaw). It does not request elevated privileges or modify other skills' configs. This persistent presence is expected for an audit/ledger tool but you should be aware it will create and later read those files.
Assessment
This skill appears to do exactly what it says: compute and verify a hard-coded origin anchor and maintain local archival/ledger files under ~/.openclaw. Before installing, review the packaged scripts (they're included) and confirm you are comfortable with files being created at ~/.openclaw/governance and ~/.openclaw/audits/moses. Because it enforces a specific genesis anchor, running it alongside other governance tooling may make chains that do not use that anchor fail verification — test in a sandbox first. Also note small metadata inconsistencies (declared bins/stateDirs vs registry fields); these are not dangerous but worth confirming. If you need stronger assurance, inspect the remaining truncated functions in the packaged files (attest/entry handling) or run the code in an isolated environment.

Like a lobster shell, security has layers — review code before you run it.

auditvk975eej3yq6bjqqakx3pwzs5gx82tyjagovernancevk975eej3yq6bjqqakx3pwzs5gx82tyjaharnessvk975eej3yq6bjqqakx3pwzs5gx82tyjaidentityvk97780cwbqaw3rg2f3xdngdn0d82r4ezlatestvk97ab388p29xdmc3xj2tbpnf1582xdcrlineagevk975eej3yq6bjqqakx3pwzs5gx82tyjamosesvk975eej3yq6bjqqakx3pwzs5gx82tyjaprovenancevk975eej3yq6bjqqakx3pwzs5gx82tyjatrustvk975eej3yq6bjqqakx3pwzs5gx82tyja

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

§ Clawdis

Comments