RepoPilot

halfrost/LeetCode-Go

✅ Solutions to LeetCode by Go, 100% test coverage, runtime beats 100% | LeetCode 题解

Mixed

Single-maintainer risk — review before adopting

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.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10

  • ⚠Single-maintainer risk — top contributor 93% of recent commits
  • ⚠Scorecard: default branch unprotected (0/10)
  • ✓Last commit 1d ago
  • ✓8 active contributors
  • ✓MIT licensed
  • ✓CI configured
  • ✓Tests present

What would improve this?

  • •Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

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: halfrost/LeetCode-Go

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T00:10:48.687Z · commit 1dde49c8ab37

Verdict

Mixed — Single-maintainer risk — review before adopting

  • Last commit 1d ago
  • 8 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

A comprehensive LeetCode problem solution repository written in Go, containing 100+ algorithm implementations with full test coverage and claimed 100% runtime performance beats. The project includes a CLI tool (ctl) for managing problem metadata, generating PDF documentation, and organizing solutions by algorithm category (arrays, trees, dynamic programming, etc.). Organized as a problem-solution monorepo with two main sections: solution implementations in language-specific directories (Go at 1.5M LOC, with Python/JavaScript alternatives), and a CLI tool (ctl/) that manages metadata, renders markdown templates by algorithm category (stored in ctl/meta/ and ctl/template/), and…

Start here

Read these in order:

  • ctl/util/util.go — Foundation: doesn't import anything internally and is imported by 6 other files. Read first to learn the vocabulary.
  • ctl/models/lcproblems.go — Foundation: imported by 3, no internal dependencies of its own.
  • ctl/render.go — Built on the foundation; imported by 0 downstream files.
  • ctl/statistic.go — Built on the foundation; imported by 0 downstream files.

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/halfrost/LeetCode-Go.git
cd LeetCode-Go
go mod download
go test ./...

Verify Go 1.19+ is installed (go version). The ctl/ subdirectory has its own go.mod for the metadata management tool.

Daily commands:

For solutions: go test ./... runs all problem tests. For CLI metadata tool: enter ctl/ directory and execute go run main.go with appropriate flags (see ctl/command.go for command definitions). PDF generation via `…

…shortened for this brief.

Key cautions & unknowns

  • Single-maintainer risk — top contributor 93% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • The ctl/models/go.mod uses a replace directive pointing to ../util, implying a local util module that must exist at ctl/util/ for builds to succeed—verify this directory exists before running go mod download…
  • 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 "Safe to depend on" badge

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

Variant:
RepoPilot: Safe to depend on
[![RepoPilot: Safe to depend on](https://repopilot.app/api/badge/halfrost/leetcode-go?axis=dependency)](https://repopilot.app/r/halfrost/leetcode-go)

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/halfrost/leetcode-go on X, Slack, or LinkedIn.

Ask AI about halfrost/leetcode-go

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

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.
Or write your own question

Similar Go repos

Other mixed-signal Go repos by stars.

More from halfrost

See all

Recent Q&A

Public conversations other people have had about this repo.

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/halfrost/leetcode-go"
  width="100%" height="500"
  style="border:1px solid #d0d7de; border-radius:8px;"
  allow="microphone"
  loading="lazy"
></iframe>