# Perseus

Perseus is an archived Go dependency visualization tool that maps how packages and modules depend on one another, helping developers trace complex dependency trees and identify problematic dependencies.

Canonical page: https://ourlocalhost.com/app/5620/perseus

## Description

Perseus is an archived Go dependency visualization tool that maps how packages and modules depend on one another, helping developers trace complex dependency trees and identify problematic dependencies.

## Platform availability

Available on 0 of 10 platforms.

## Health score

29/100 (Low), based on 5 of 5 factors.
- Maintained: 0 (GitHub repository is archived)
- Popular: 33 (44 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 50 (2 GB minimum RAM)
- Security check: 70 (no serious findings, 7 minor, CI, tests)

## Links

- GitHub: https://github.com/CrowdStrike/perseus

## Common questions

### What database should I provision for Perseus?

It uses PostgreSQL rather than a specialized graph database. One caveat is that Amazon RDS currently does not support the pg-semver extension that Perseus uses for storage.

### Can Perseus show downstream dependents for private modules?

Perseus targets downstream dependency queries that the go CLI and public package sites do not cover. The README notes that pkg.go.dev will not help for private modules and does not show dependent versions.

### Why did simple grep-based dependency searches become unreliable after moving to Go modules?

Engineers no longer keep the entire monorepo under $GOPATH/src, and local workspaces are usually limited to modules they work on directly. That makes it hard to see which other modules depend on a given package.

### Where can I review the change history?

The repository points to CHANGELOG.md for a detailed history of changes.

---
Source: Our Local Host (https://ourlocalhost.com/app/5620/perseus), the self-hosted and open-source app directory.
