npm Python not analyzable deep scan unknown

wazionapps/nexo

v7.38.0
npm

not analyzable — repository too large to download in full

NEXO runtime core for NEXO Desktop: local memory, automation, MCP tools and update-managed runtime.

maintainer
wazionapps
licence
NOASSERTION
first seen
2026-05-22
last seen
2026-07-04
releases · 30d
0
short id
risk insufficient evidence

Insufficient evidence to grade. This server's source has not been statically analyzed, so a low grade would only mean "nothing found", not "nothing there". We don't show a reassuring grade we can't stand behind. Attested signals (CVEs, provenance) below still apply.

Once the source is analyzed (see the analysis flag in the header), a graded score appears here. How analysis works: methodology.

risk trajectory 2 movements
  • B · 19 A · 11
  • B · 15 B · 19
capability exposure grade factor +16
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

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