ByteRover's CLI
- capability exposure inferred + 26
- tool safety inferred + 17
- trust mitigators mixed − 5
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 1w ago · see ecosystem CVEs →
- B · 33 → C · 38
- B · 30 → B · 33
- C · 35 → B · 30
- B · 23 → C · 35
- B · 19 → B · 23
- A · 0 → B · 19
No known CVEs for this server.
- high dangerous code
obfuscated payload: dynamic require()/import()
- 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)
- low 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
analyzed commit 1052ac1 · analyzer v33 · 1w ago
skills & prompt files 4
[](https://mcpobservatory.com/servers/github:campfirein/byterover-cli/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 campfirein.