Deps
Deps is a collection of ready-to-use virtual environments for testing versioning tools across different operating systems and hardware.
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.
69/100 Good
- Maintained
- 94last commit 39 days ago
- Popular
- 53462 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 602 GB minimum RAM, runs on ARM
- Security check
- 90no serious findings, CI, tests, OpenSSF Scorecard 7.4/10
- GitHub stars
- 462
- Open issues
- 63
- Last commit
- 2026-10-13
- License
- Apache-2.0
- Activity
- declining
Checked 15 days ago - source: GitHub (google/deps.dev)
Resources & Compatibility
Minimum requirements: 2 GB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install and check the wit-deps tool Run `cargo install wit-deps-cli`, then run `wit-deps --help` to confirm it works. This installs the command-line tool; without it, you can't fetch or lock your dependency files. source
- Add your dependencies in wit/deps.toml Create or edit `wit/deps.toml` to list each dependency as a URL or local folder path, and give every entry either `url` or `path`. This file is the recipe the tool follows, and missing or wrong entries make locking fail. source
- Fix broken dependencies with a fresh lock If a dependency download breaks or gets out of sync, delete the `wit/deps` folder and run `wit-deps lock`. That clears the saved files and starts a clean install, which avoids confusing half-downloaded state. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How can I verify the dependency CLI is installed?
Run cargo install wit-deps-cli, then run wit-deps --help to confirm it works. Without the command-line tool, you cannot fetch or lock dependency files.
Where do I declare dependency sources for locking?
Create or edit wit/deps.toml and list each dependency as a URL or local folder path. Every entry must have either url or path, because missing or wrong entries make locking fail.
How do I recover from a broken or out-of-sync dependency download?
Delete the wit/deps folder and run wit-deps lock. That clears the saved files and starts a clean install.
Does deps automate dependency update work?
It runs updates, automates pull requests, and keeps local installations in check.
Answers sourced from github.com, github.com, github.com, github.com
Community
- Self hosted code development environment with Github integration? - Reddit (reddit)
- Difference between indoor, deps, exotics ect : r/trees - Reddit (reddit)
- booked a job, been in DEP for 5 months - my personal ... - Reddit (reddit)
- How long did you wait in DEP? What do you think of these jobs? (reddit)
Collected 48 days ago - public community threads