go-mem0@0.1.2
CAUTIONPublisher claims: "Unofficial Go client for the Mem0 Platform API, generated with oapi-codegen. Package `mem0` (`github.com/psyb0t/go-mem0`) provides `mem0.NewClientWithResponses` with a typed `...WithResponse` method for every endpoint, covering adding, searching, listing, updating and deleting memories (V1, V2 and V3), entities, events, exports, organizations, projects, webhooks, profiles and Dream operations. Auth is an API key in the `Authorization` header with a `Token` prefix, added through a request editor. Use when Go code needs Mem0 hosted memory or already imports go-mem0." 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-27 and scored it 67/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 findings across 265 lines in 3 files.
What would make this Verified
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim psyb0t: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.