RepoPilot

google/wire

Compile-time Dependency Injection for Go

Mixed

Stale — last commit 1y ago

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

last commit was 1y ago; Scorecard "Token-Permissions" is 0/10

  • Stale — last commit 1y ago
  • Scorecard: marked unmaintained (0/10)
  • 26+ active contributors
  • Distributed ownership (top contributor 36% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days

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: google/wire

Generated by RepoPilot · document generated 2026-09-14 · concise human review Evidence snapshot · analyzed 2026-09-14T04:34:08.477Z · commit 9c25c9016f68

Verdict

Mixed — Stale — last commit 1y ago

  • 26+ active contributors
  • Distributed ownership (top contributor 36% of recent commits)
  • Apache-2.0 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

Wire is a compile-time code generation tool for Go that automates dependency injection by analyzing function signatures and generating initialization code. Rather than using runtime reflection or global state, Wire generates explicit wiring code that connects components—solving the boilerplate problem of manual dependency injection in Go applications while keeping the generated code readable and debuggable. Single-module layout: internal/wire/ contains the core analysis engine (analyze.go, parse.go, copyast.go, errors.go) with extensive testdata under internal/wire/testdata/ organizing ~15+ test scenarios (each with foo/, pkg/, want/ subdirectories for inputs and golden outputs). cmd/wire…

Start here

Read these in order:

  • wire.go — Foundation: doesn't import anything internally and is imported by 91 other files. Read first to learn the vocabulary.
  • internal/wire/analyze.go — Foundation: imported by 1, no internal dependencies of its own.
  • internal/wire/testdata/BindInjectorArg/foo/wire.go — Built on the foundation; imported by 0 downstream files.
  • internal/wire/testdata/BindInjectorArgPointer/foo/wire.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.

Clone the repository:

git clone https://github.com/google/wire.git
cd wire

Install the wire command-line tool:

go install ./cmd/wire

Verify installation by checking the generated help:

wire -help

Daily commands:

Wire is a code generation tool, not a runtime service. To use it on a Go project:

cd your-go-project
wire ./...

This scans for wire.go files, analyzes dependencies, and generates wire_gen.go files. To run Wire's own test suite:

sh internal/runtests.sh

…shortened for this brief.

Key cautions & unknowns

  • Stale — last commit 1y ago
  • Scorecard: marked unmaintained (0/10)
  • Wire operates at compile time and requires wire.go files with specific syntax (see testdata examples for syntax patterns). The project is unmaintained, so compatibility with Go versions beyond 1.19 is untested—verify…
  • 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/google/wire?axis=dependency)](https://repopilot.app/r/google/wire)

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/google/wire on X, Slack, or LinkedIn.

Ask AI about google/wire

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