Generate crate dependency graphs on the web with my latest project: crate-deps


Try it out here:

Let me know if you have any thoughts or ideas!

Also, if anyone is aware of any discounts/credits for Heroku for open source projects, please let me know (currently paying out of pocket to keep this up).


Oh my, this is so cool! Some thoughts:

  • Perhaps edges for build-dependencies, dev-dependencies, and normal dependencies could be separate colors? It’d be cool to see what portions of the dependency graph are only used for tests, build scripts, or at runtime. I suppose that propagating the color may be… difficult though :smile:
  • How come this needs the paying tier of Heroku? I figured something like this would work on the free tier? (I really want to see this stay alive!)
  • I have a feeling this would be even more hard than usual, but being able to specify a git repo (e.g. Servo or Cargo) would also be super awesome to get a picture of the dependency graph. Checking out all of Servo/Cargo, though, may not be worth it!

Again, this is awesome!


I think if you wanted to get super-brownie points with a bunch of Rust skeptics, the ability to identify which repos transitively introduce unsafe seems to be pretty popular at the moment. The knowledge that you aren’t pulling in any new unsafe code would mellow several angsty people.


This would be pretty easy to do. I would just have to decide on edge color and/or style (dotted, dashed, etc) for the different dependency types. If anyone has ideas or opinions with regard to that, let me know.

So with the beta pricing, I either need the instance to sleep for four hours a day or pay $7+ a month. At the time of writing the initial post I had it on the $7/month (Hobby tier I think). With the traditional pricing, I’m not sure if the instance needs to sleep or not for the free tier. Though after doing a little research right now, it looks like it doesn’t need to sleep, so I’ll just leave it on traditional pricing for now.

This would be cool, though a little more work than time I have for right now

For this to happen, the crate metadata from this repository would need to keep track of which crates contain unsafe code.


This is so very awesome! How hard was it to get Rust running on Heroku? Does that knowledge exist somewhere, or did you have to figure it out?

I’m a huge fan of both, so I’ll probably poke through your code and write a web app using Rust :slight_smile:


I just put together a minimal example (and a quick tutorial) on how to deploy a Hello World server using Heroku with tiny_http. Let me know if you have any clarification questions or suggestions for improvement with any part of the process :smile: