Progressive algorithmization toolchain — from LLM to deterministic code, from proxy to tickets
- capability exposure inferred + 35
- tool safety inferred + 12
inferred
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
grade last moved 5d ago · see ecosystem CVEs →
- C · 59 → C · 47
- C · 35 → C · 59
No known CVEs for this server.
- high dangerous code
dynamic exec: eval()/exec(), unsafe yaml.load()
- low dangerous code
env-secret-flows-to-network-py: An environment value reaches a network call. Review whether it is a credential leaving the process; the ordinary API-wrapper shape (read a key, call
- low dangerous code
env-secret-flows-to-network-py: An environment value reaches a network call. Review whether it is a credential leaving the process; the ordinary API-wrapper shape (read a key, call
- low dangerous code
env-secret-flows-to-network-py: An environment value reaches a network call. Review whether it is a credential leaving the process; the ordinary API-wrapper shape (read a key, call
analyzed commit 5a99bda · analyzer v33 · 1d ago
danger signals2
- dynamic code execution eval()/exec() semcod-algitex-5a99bda/examples/19-local-mcp-tools/buggy_code.py :26
config = eval(source) # Błąd: code injection - dynamic code execution unsafe yaml.load() semcod-algitex-5a99bda/examples/20-self-hosted-pipeline/buggy_code.py :41
return yaml.load(config_string)
[](https://mcpobservatory.com/servers/github:semcod/algitex/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of semcod.