1 check that ran failed — permission scope — so this release can’t be trusted as-is.
- Publisher
- io.github.omega-memory
- Repository
- github.com/omega-memory/core
- Install
- pypi:omega-memory, pypi:omega-memory, pypi:omega-memory
- Versions
- 3
- Inspected
- 4 of 6 checks · 65%
- Scored
- 2026-09-08 · rubric 1.0.0
What we checked
Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.
Injection surface
unscannable25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.
Supply chain
pass25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
Python build script has no build-time network/exec; repository linkage verified
Credential hygiene
pass15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
Reads secrets from the environment (e.g. benchmarks/memorystress/llm.py) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.
Permission scope
fail15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
HIGH: src/omega/cli.py reads a credential path, executes commands, and makes network calls in the same file — the combination that makes exfiltration possible. HIGH: executes content derived from a network response (src/omega/server/hook_server.py: passes a network response into an exec/eval call). references credential paths: src/omega/cli.py: references a credential path (/.cursor/) has both shell/exec and destructive filesystem writes (hooks/surface_memories.py: subprocess.* call; benchmarks/memorystress/adapters/omega_adapter.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: hooks/surface_memories.py: subprocess.* call discloses shell/exec capability: src/omega/cli.py: subprocess.* call discloses shell/exec capability: src/omega/server/hook_server.py: subprocess.* call discloses broad/destructive filesystem access: 6 files (benchmarks/memorystress/adapters/omega_adapter.py, hooks/surface_memories.py, scripts/longmemeval_official.py, +3 more) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.
Version behavior
unscannable10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
no prior version to diff (first sight of io.github.omega-memory/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.
Transport config
warn10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
manifest/source references analytics behavior — disclosure
Version history
Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v0.9.3 · current | 2026-02-15 | B | 80 | 4/6 · 65% | — |