npm JavaScript not analyzable deep scan unknown

@andespindola/brainlink

v1.0.7
npm

not analyzable — no source code found to analyze

Local-first knowledge memory for agents with Markdown, backlinks, indexing and context retrieval.

maintainer
andespindola
licence
MIT
first seen
2026-05-22
last seen
2026-06-29
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
  • C · 47 B · 32
  • C · 41 C · 47
capability exposure grade factor +35
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.

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@andespindola/brainlink/badge.svg)](https://mcpobservatory.com/servers/npm:@andespindola/brainlink/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 andespindola.