Is go-micro maintained?

GraphCanon rates go-micro "Very active" (96% maintenance signal from public GitHub metadata, computed 2d). Last push was 0 days ago. 30 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

Is go-micro safe to use?

Last scanned 1mo (deps profile). Status: 65 low - 65 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify go-micro as safe - review maintenance, provenance, and scan findings on this page before adopting.

No. go-micro is not flagged as a fork in GitHub metadata at the time of the last refresh.

Does go-micro have known security vulnerabilities?

Last scanned 1mo (deps profile). Status: 65 low - 65 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.

How often is the go-micro trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2d (methodology github_public_v1).

What does GraphCanon never claim about go-micro?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for go-micro. Signals are sourced heuristics with explicit limits - see trust methodology (https://www.graphcanon.com/trust-methodology).

How does GraphCanon assess trust for go-micro?

Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology (https://www.graphcanon.com/trust-methodology) for full scope and limits.

Home/go-micro/Trust report

Trust and health report

go-micro - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated 2d · GitHub synced 2d

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Very active96% signal

last push 0d ago · last release 2d · 30 releases (90d)

+55 stars (30d) · 0 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 29217054
Not a fork
Verified publisher: organization account
Computed 2d

Security intelligence

Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.

OSV dependency advisories

Published findings

Last query: 1mo
Scanner: osv@v1
Stored findings: 65

View source evidence

deps.dev advisories

Not queried

Scanner: deps.dev@v1

View source evidence

OpenSSF Scorecard

Not queried

Scanner: openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-fw7p-63qq-7hpr

filippo.io/edwards25519@v1.1.0 · osv@v1

go.sum

GO-2026-4503

filippo.io/edwards25519@v1.1.0 · osv@v1

go.sum

GHSA-jqcq-xjh3-6g23

github.com/jackc/pgproto3/v2@v2.3.3 · osv@v1

go.sum

GO-2026-4518

github.com/jackc/pgproto3/v2@v2.3.3 · osv@v1

go.sum

GHSA-j88v-2chj-qfwx

github.com/jackc/pgx/v4@v4.18.3 · osv@v1

go.sum

GO-2026-5004

github.com/jackc/pgx/v4@v4.18.3 · osv@v1

go.sum

GHSA-3f24-pcvm-5jqc