HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
golang
dep
Go2017–2023
golang / dep · Archived

dep

Go dependency management tool experiment (deprecated)

46Distinct people
48Mentions
0Explicit recommenders
12.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Go dependency management tool experiment (deprecated)

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:58 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year48 dated mentions

Observed mentions: 2017-01-24 16:39:45 UTC to 2023-01-10 02:44:15 UTC.

05101520252017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 25 mentions; 7 submissions, 18 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 20 mentions; 0 submissions, 20 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC25718
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC20020
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Dep dep is a dependency management tool for Go. It requires Go 1.9 or newer to compile. NOTE: Dep was an official experiment to implement a package manager for Go. As of 2020, Dep is deprecated and archived in favor of Go modules, which have had official support since Go 1.11. For more details, see https://golang.org/ref/mod. For guides and reference materials about dep, see the documentation. Installation You should use an officially released version. Release binaries are available on the releases page. On MacOS you can install or upgrade to the latest released version with Homebrew: $ brew install dep $ brew upgrade dep On Debian platforms you can install or upgrade to the latest version with apt-get: $ sudo apt-get install go-dep On Windows, you can download a tarball from go.equinox.io. On other platforms you can use the install.sh script: $ curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh It will install into your $GOPATH/bin directory by default or any other directory you specify using the INSTALL_DIRECTORY environment variable. If your platform is not supported, you'll need to build it manually or let the team know and we'll consider adding your platform to the release builds. If you're interested in getting the source code, or hacking on dep, you can install via go get: go get -u github.com/golang/dep/cmd/dep
Read the full README on GitHub

What Hacker News says

25 sources
Okay, let's say I agree with your arguments: 1. Go "is still not as fast as Java can be" [1] 2. "Go lacks the most basic tools which any seasoned developer can expect from a language (like generics)" 3. "Go does not have a de facto build system and you can’t handle dependency management in an easy way" [2] 4. odd error handling 5. not a lot of libraries to choose from [3] 6. possibly more arguments that I missed when summarizing your post The way you paint it, people would be stupid to use Go. However, thousands of very talented developers use Go everyday. How can you explain this disconnect? [1] I like how you didn't say that Go "is not as fast as Java". That's a subtle, but important difference. [2] `go install` is the build system and I have solved dependency management for myself with literally a small shell script [4], and an officia
Read the rest
l solution is in the works [5]. [3] I never had trouble finding libraries for use-cases both common and obscure). [4] https://github.com/holocm/golangvend [5] https://github.com/golang/dep
In Re: Moving from PHP to Go and Back Again
I'm not even going to bother. Nuget is such a pile of rubbish it's not even worth arguing about; if that's the best package manager you've ever used, you should really go check https://github.com/fsprojects/Paket out. (they also helpfully articulate why nuget isn't really very good) The irony is that the folk from go-world have finally acknowledged the package management solution they have is really terrible, and they're building a lovely new one (https://github.com/golang/dep). Maybe sometime in the future you'll be eating your words, when go has a lovely package manager. ...and c# still has nuget. :)
In Span in C#
First a note, godep is a different tool then the one you mean [1], that does the same. > dep still has nasty bugs, but in general these are comparable or fewer to other tools out there. (From the Github readme) I started a project about two months ago and wanted to use Dep, however there were a few show stopping issues for that. Most prominently Go has issues with upppercase/lowercase repositories, meaning if one of your dependencies imports github.com/Sirupsen/logrus, and you or another dependency imports github.com/sirupsen/logrus your code won't compile, no matter if you are on a case sensitive system or a case-insensitive system. [2] The aforementioned logger made a switch in the naming which caused problems while most were migrating the import. The docker distribution in its latest stable version still uses uppercase, while others us
Read the rest
e the lowercase. Dep follows the Go specifications and at the moment just throws an error, before, they didn't handle it at all. So I had to resort to a different dependency management for now, which did some linking to fix the situation. [1]https://github.com/tools/godep [2]https://github.com/golang/dep/issues/1010
In Go: Ten years and climbing
There are a lot of problems with this approach and a few errors in the post, but I'm just going to highlight the most significant one: > If the project uses CI/CD or just for consistency, it is good to keep the list of dependencies used in packages. This is done by the “deps” task, which should get all the necessary dependencies by “go get” command. This is a very strong anti-pattern. Everyone should be using a dedicated version management tool (ideally dep[0], but there are others), which handles this seamlessly and behind the scenes. Introducing another place where dependencies are tracked and can be installed is a recipe for problems down the line. [0] https://github.com/golang/dep/
In Golang: Don't be afraid of makefiles

Showing the 15 most recent of 25 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.