ipfs-pin@0.1.1
CAUTIONPublisher claims: "IPFS content persistence for OpenClaw via a local kubo node. Adds files to IPFS, pins them so they stay robust while active, and tracks a per-file TTL in a ledger. `decay` unpins entries not referenced within their TTL and garbage-collects the repo; a systemd user timer runs it daily so unused content decays naturally without manual cleanup. Reports only CIDs and status the ipfs CLI actually returned." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-29 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
No other findings across 522 lines in 3 files.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim paradoxfuzzle: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.