.png)

Command-line interface for DepsDiver - analyze packages, repositories, users, and threat actors
We recommend verifying the checksum of the Diver binary to ensure the downloaded file has not been modified or tampered with.
Using sha256sum:
sha256sum -c diver_0.2.3_checksums.txt --ignore-missing
If sha256sum is not available on macOS:
shasum -a 256 -c diver_0.2.3_checksums.txt --ignore-missing
PowerShell:
certutil -hashfile diver_v0.2.3_file.tar.gz SHA256
Compare the resulting hash with the corresponding entry in the checksum file.
Download the appropriate archive for your platform and extract the diver binary:
tar -xvf diver_v0.2.0_Darwin_arm64.tar.gz
This will extract a diver executable into the current directory.
The following commands assume you are running diver from the directory where the binary was extracted.
Use command line flags to provide configuration directly when running diver:
./diver -u https://depsdiver.com/api -t <token>
Set environment variables once and run diver without repeating flags:
export DEPS_DIVER_API_TOKEN=<token>
export DEPS_DIVER_URL=https://depsdiver.com/api
./diver
Currently diver supports API tokens, which can be generated in your
DepsDiver account.
Convert raw telemetry into definitive threat reports. Map adversarial influence across specific packages, repositories, and contributors in your stack.
Get a report for a single package:
./diver get go github.com/mailru/easyjson
where ecosystem is one of: go, npm, pypi, maven, cargo, rubygems, or nuget
Get FOCI data for a package:
./diver get fi npm:fast-glob
Get detailed package metadata:
./diver get package npm:fast-glob
This command returns a repository ID, which can be used for repository-level reports.
First, retrieve the repository ID from the package:
./diver get package npm:fast-glob
Then, get the commit count for the repository:
./diver get commit-count <REPO_ID>
Get the OpenSSF Scorecard for a repository:
./diver get scorecard <REPO_ID>
Get repository releases:
./diver get releases <REPO_ID>
Get repository tags:
./diver get tags <REPO_ID>
Get data for a threat actor by email or username:
./diver get threat-actor <email-or-username>
First, retrieve the user ID from the threat-actor search:
./diver get threat-actor <email-or-username>
Then, get the user's data:
./diver get user <USER_ID>
./diver get user file:file-of-user-ids.txt
./diver get users <REPO_ID>
./diver get users file:file-of-repo-ids.txt
2026 All Rights Reserved | Hunted LabsWe value your privacy. The site uses necessary cookies to operate and maintain security, which
are set automatically. We also use analytics cookies to understand how visitors use this site so we can improve it. These cookies are only placed with your consent. No analytics data is collected if you decline. You can change your preference at any time via the "Cookie Preferences" link in the footer below. For more information, see our Privacy Policy.
We value your privacy. We use analytics cookies to understand how visitors use this site so we can improve it. These cookies are only placed with your consent. No analytics data is collected if you decline. You can change your preference at any time via the "Cookie Settings" link at the bottom of this page. For more information, see our Privacy Policy.