heroiclabs/nakama · Architecture

A static read of how heroiclabs/nakama is wired together — module coupling, layering, and circular dependencies — derived from its import graph.

Architecture Security & risks Dependencies License Maintenance Alternatives Vs Full analysis

Architecture grade

score 99/100

Import cycles

lower is better

338

Modules parsed

89 edges

98%

Layeredness

clean-layer ratio

Most-depended-on modules

These are the highest-fan-in files — change them and the blast radius is largest. Read them first.

console/console.pb.go31 importers · radius 33
social/social.go14 importers · radius 15
internal/gopher-lua/_state.go8 importers · radius 8
internal/cronexpr/cronexpr.go8 importers · radius 8
console/acl/acl.go5 importers · radius 5
internal/satori/satori.go3 importers · radius 3
internal/gopher-lua/parse/lexer.go3 importers · radius 11
internal/gopher-lua/ast/ast.go3 importers · radius 14

Modules (4)

Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.

internal/gopher-lua5 files · 8 in-degree
console/acl2 files · 5 in-degree
internal/gopher-lua/parse2 files · 3 in-degree
server53 files · 2 in-degree

Ask AI about heroiclabs/nakama

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

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.