dependency graph
The most active recent releasers that cluster together — laid out by who maintains them and what they depend on. This is a selection of active, connected nodes (at least one release in the last 30 days), not a census of the whole ecosystem. Each node is coloured by its composite-risk grade (A safest → E most exposed) and sized by how many other servers depend on it — so the network reads as attack surface. Edges join servers that share a maintainer or a runtime dependency. Watch it live — each release pulses its node and sends a blip down its edges. Click any node to open the server; see the full ranking at /security/risk.
- D · high 5
- C · elevated 29
- B · low 19
- A · minimal 117
- ungraded 11
- dependency 10
- same maintainer 392
- both 17
- ai 18
- agentdb 4
- neural 3
- ruvector 3
- mcp-ts-core 2