github TypeScript re-analysis due

usekaneo/kaneo

github

🎯 All you need. Nothing you don't. Open source project management that works for you, not against you.

maintainer
usekaneo
licence
MIT
first seen
2026-08-11
last seen
2026-09-10
releases · 30d
18
short id
risk 53/100 · heuristic grade
C elevated inferred analyzer v33 (current)
  • capability exposure inferred + 32
  • recent drift inferred + 20
  • tool safety inferred + 17
  • trust mitigators mixed − 16

inferred mixed

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 3d ago · see ecosystem CVEs →

risk trajectory 4 movements
  • C · 48 C · 53
  • C · 51 C · 48
  • C · 59 C · 51
  • C · 51 C · 59
capability exposure grade factor +32
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety 3 findings · grade factor +17
  1. high dangerous code

    committed secret: committed .env

  2. medium dangerous code

    env-secret-flows-to-network-js: A process environment value reaches a network call. Review whether it is a credential leaving the process; the ordinary API-wrapper shape (read a ke

  3. medium toxic flow (lethal trifecta)

    lethal trifecta reachable across this server's tool + source surface: private-data access + untrusted-content ingestion + network exfil (a leg is proven only in the analyzed source)

skills & danger signals github-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed commit 1d2ca49 · analyzer v33 · 3h ago

skills & prompt files 20

danger signals3

other grade factors evidence elsewhere
embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:usekaneo/kaneo/badge.svg)](https://mcpobservatory.com/servers/github:usekaneo/kaneo/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 usekaneo.