npm JavaScript not analyzable deep scan unknown

instar

v1.3.1244
npm

not analyzable — repository too large to scan in full (large monorepo)

Coherence infrastructure for self-evolving AI agents — on the Claude Code or Codex subscription you already have.

maintainer
jkheadley
licence
MIT
first seen
2026-05-24
last seen
2026-09-17
releases · 30d
64
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 7 movements
  • C · 39 B · 34
  • C · 51 C · 39
  • C · 39 C · 51
  • C · 54 C · 39
  • C · 49 C · 54
  • C · 47 C · 49
  • A · 12 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 2 findings · grade factor +7
  1. 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)

  2. low exfiltration combo threadline_request_secret

    single tool reads + sends: net, secrets

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