npm JavaScript not analyzable

@metaharness/kernel

v0.4.5
npm

not analyzable — no source code found to analyze

MetaHarness — mint a custom AI agent harness from any repo. Browser Studio + `npx metaharness` CLI. Runs on Claude Code, Codex, pi.dev, Hermes, OpenClaw, RVM, Prime Agent.

maintainer
ruvnet
license
MIT
first seen
2026-06-13
last seen
2026-08-14
releases · 30d
7
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 19 movements
  • A · 1 A · 13
  • B · 32 A · 1
  • A · 1 B · 32
  • B · 32 A · 1
  • A · 1 B · 32
  • B · 32 A · 1
  • A · 1 B · 32
  • B · 32 A · 1
  • A · 1 B · 32
  • B · 32 A · 1
  • A · 1 B · 32
  • B · 32 A · 1
  • A · 1 B · 32
  • B · 32 A · 1
  • A · 1 B · 32
  • B · 32 A · 1
  • A · 1 B · 32
  • B · 32 A · 1
  • A · 1 B · 32
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.

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:ruvnet/agent-harness-generator/badge.svg)](https://mcpobservatory.com/servers/github:ruvnet/agent-harness-generator/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 ruvnet.