RepoPilot

x-motemen/gore

Yet another Go REPL that works nicely. Featured with line editing, code completion, and more.

Healthy

Healthy across all four use cases

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Small team — 2 contributors active in recent commits
  • Single-maintainer risk — top contributor 97% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 6w ago
  • 2 active contributors
  • MIT licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Informational only. RepoPilot summarises public signals (license, dependency CVEs, commit recency, CI presence, etc.) at the time of analysis. Signals can be incomplete or stale. Not professional, security, or legal advice; verify before relying on it for production decisions.

Repository brief

Repo brief: x-motemen/gore

Generated by RepoPilot · document generated 2026-09-14 · concise human review Evidence snapshot · analyzed 2026-09-14T17:13:00.716Z · commit 115ca4748893

Verdict

Healthy — Healthy across all four use cases

  • Last commit 6w ago
  • 2 active contributors
  • MIT licensed
  • CI configured
  • 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

gore is a Go REPL (Read-Eval-Print Loop) that executes arbitrary Go expressions, statements, and function declarations interactively with line editing, history, code completion via gopls, and package auto-importing. It solves the problem of interactive Go development by wrapping go run to provide a Bash-like shell experience for the Go language. Monolithic design: cmd/gore/main.go is the entry point; core logic lives in gore.go, session.go, and commands.go; terminal interaction is abstracted via liner.go (line editor) with platform-specific stubs (terminal_unix.go, terminal_windows.go); LSP integration via gopls.go; error handling and filtering in errfilter.go. CLI wrapping is minimal,…

Start here

Read these in order:

  • command_name.go — Foundation: doesn't import anything internally and is imported by 2 other files. Read first to learn the vocabulary.
  • cli/cli.go — Built on the foundation; imported by 1 downstream file.
  • cli/cli_test.go — Built on the foundation; imported by 0 downstream files.
  • cmd/gore/main.go — Layer 2 — application-level code that wires the lower layers together.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/x-motemen/gore.git
cd gore
go install ./cmd/gore
gore

Optional: go install golang.org/x/tools/gopls@latest for code completion. Verify your Go toolchain is installed and in PATH.

Daily commands:

Start the REPL:

gore

Then enter Go code at the prompt (e.g., fmt.Println("hello")), or use built-in commands like :help, :type <expr>, :doc <pkg>, :quit. Multi-line input is supported. History is saved to $GORE_HOME (default `~/…

…shortened for this brief.

Key cautions & unknowns

  • Small team — 2 contributors active in recent commits
  • Single-maintainer risk — top contributor 97% of recent commits
  • Scorecard: default branch unprotected (0/10)
    1. Repeated execution: Every input is re-evaluated by re-running the accumulated code, so expressions like time.Now() will return different values on each input. This is a design trade-off documented in FAQ #67.…
  • Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.


For the complete agent context, use the CLAUDE.md or Cursor rules export.

Save as

Full context for agent files, or a concise PDF for human review.

View complete agent reference

Open to load every section of the agent reference.

Want this for your own repo?

Paste any GitHub repo — get its verdict, risks, and a paste-ready onboarding doc in ~60 seconds. Free, no sign-up.

Embed the "Healthy" badge

Paste into your README — live-updates from the latest cached analysis.

Variant:
RepoPilot: Healthy
[![RepoPilot: Healthy](https://repopilot.app/api/badge/x-motemen/gore)](https://repopilot.app/r/x-motemen/gore)

Paste at the top of your README.md — renders inline like a shields.io badge.

Preview social card

This card auto-renders when someone shares https://repopilot.app/r/x-motemen/gore on X, Slack, or LinkedIn.

Ask AI about x-motemen/gore

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question
Embed this chat in your README

Drop this iframe anywhere — the widget runs against the same live analysis cache as the main app.

<iframe
  src="https://repopilot.app/embed/x-motemen/gore"
  width="100%" height="500"
  style="border:1px solid #d0d7de; border-radius:8px;"
  allow="microphone"
  loading="lazy"
></iframe>