Getting started
Deptools reads the build file of your project and resolves the full dependency tree, including transitive dependencies. It then measures every package it finds and turns the result into one health score from 0 to 10.
For now, it reads Maven, Gradle, npm, sbt and Composer build files. If your project declares its dependencies another way, none of the pages below apply yet. See supported ecosystems for the exact files that are read.
Where to start
| If you | Start with |
|---|---|
| Want to see a real report before signing up | Try the demo |
| Have a repository on GitHub | Quickstart |
| Do not host your code on GitHub | Analyze a project without GitHub |
The demo needs no account. The quickstart takes you from signing up with GitHub to a first analysis of a public repository. The Free plan covers 10 public projects.
The third path exists because Deptools reads your build files through its own GitHub App. Without GitHub, your pipeline pushes those files to Deptools instead. That path requires the Pro plan.
After your first analysis
You end this chapter on a dashboard: scores, the packages that pull it down, and the graph they sit in. The health score explains where that number comes from, what its six dimensions measure, and why it moves between two analyses of the same commit.