A high functioning package detective.
Author caseykneale
35 Stars
Updated Last
1 Year Ago
Started In
February 2020


Stable Dev Build Status Codecov Build Status


The goal for Sherlock is to make it easy to create design document charts, and interrogate packages from a "high level" either visually or programmaticly (from the REPL, or whatever). This was started because someone wanted some design document things from another project. So, rather then go through that drudgery it seemed most appropriate to make a tool that let's people do this for everyone - easily.

Whats displayed?

  • Types, Abstract Types, Functions, Dynamically Typed items, and Undefined exports are all displayed.
  • First order connections between these items are all visible and stored in a Graph structure backend.
  • Second or higher order connectivity is not currently guaranteed. (IE: the relationship between ConcreteType and AbstractType2 in the following example: ConcreteType <: AbstractType1{AbstractType2}, will not be displayed except maybe in the TypeTree plot ).
  • Macros are also not displayed because these puppies dynamically generate code, that's just out of the scope of this project for now.
  • Types which do not belong directly to an inspected Module are also not displayed. Think of how confusing that could be?

There are 2 options for displaying the visualizations herein: the WebUI or the command line.


using Sherlock



using LightGraphs, GraphRecipes, Plots
using Sherlock

d = Detective( Sherlock )
#what's connected to what
#what types are in this module?
#plot a normal sherlock overview plot
#Zoom in on a specifc item in the detective instance
magnify( d, :Detective )

The current state of the code is somewhere between "hot mess" and "early Sunday morning hacking away". If anyone would like to contribute to making this package either more robust, more information rich, or more clean I'd really appreciate it!

Used By Packages

No packages found.