Perseus

Perseus is an archived Go dependency visualization tool that maps how packages and modules depend on one another, helping developers trace complex dependency…

  • Development
  • Tools & Utilities
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

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

29/100 Low

Maintained
0GitHub repository is archived
Popular
3344 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
502 GB minimum RAM
Security check
70no serious findings, 7 minor, CI, tests
GitHub stars
44
Open issues
9
Last commit
2025-10-24
Latest release
v0.24.0
License
MIT
Activity
stale

Checked 3 days ago - source: GitHub (CrowdStrike/perseus)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install Perseus packages first Use pnpm (a tool that installs code libraries) to add @khanacademy/perseus and @khanacademy/perseus-core, and also install the expected peer packages such as React and Wonder Blocks (the reusable UI parts Perseus relies on). Without them, the app cannot build or the Perseus components will not work. source
  • Add required Perseus dependencies Wrap Perseus in a React context (a way to pass shared settings to components) and provide the required dependencies for analytics, URL generation, and video status. If you skip this, Perseus may fail to render or video and links may not behave correctly. source
  • Install Perseus is published as a Go module, so install it into a Go project from its pkg.go.dev page. source
  • Installation Perseus is distributed as a Go module (pkg.go.dev/github.com/CrowdStrike/perseus); install it from source using the Go toolchain. The repository has been archived, so the project is no longer actively maintained. source
  • Repository Archived The CrowdStrike/perseus GitHub repository has been archived. Perseus remains functional but no longer receives updates, fixes, or support. source
  • Installing via Go Perseus is distributed as a Go package. Install with: go install github.com/CrowdStrike/perseus@latest source

Fetched 7 days ago - each note links to its source

Alternatives

No alternatives collected yet.

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.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads