Service map

A static call graph goes dark at the network boundary. Codemaps stitches each repo's contract surface — .codemaps/contracts.json from codemaps init, never source — into one cross-service graph.

event:invoice.paidhttp:GET /v1/invoiceshttp:GET /v1/invoicesbilling2 served · 0 called · 1 eventscheckout1 served · 2 callednotifications0 served · 1 called · 1 events
sample workspace · 3 reposdrag to pan · scroll to zoom · click a node or edgesolid = http/rpc · dashed = events · thickness = contracts · opacity = confidence
Blast radius — the money question
If acme/billing changes http:GET /v1/invoices, it breaks 2 consumers — acme/checkout, acme/notifications. Answered before you ship it, not after the pager goes off.

Services

acme/billing 2 served · 0 called · 1 events
acme/checkout 1 served · 2 called · 0 events
acme/notifications 0 served · 1 called · 1 events

Cross-service edges (3)

acme/billing → acme/notifications event:invoice.paid [event, 0.44] call src/events.ts:22
acme/checkout → acme/billing http:GET /v1/invoices [http, 0.6] call src/billing-client.ts:30
acme/notifications → acme/billing http:GET /v1/invoices [http, 0.6] call src/digest.ts:51

Dangling calls (external SaaS / unindexed repos)

acme/checkout: http:POST /v1/charges
Map your own repos — paste contracts.json from two or more