SourceGraph: Use graph-theory to analyse your code

[ development, program ] [ Propose Tags ]

Statically analyse Haskell source code using graph-theoretic techniques.

To use SourceGraph, call it as either:

SourceGraph path/to/Foo.cabal

Or, if your project doesn't use Cabal, then there is limited support for using an overall module from your program/library:

SourceGraph path/to/Foo.hs

Note that the Cabal method is preferred, as it is better able to determine the project name and exported modules (when passing a Haskell file to SourceGraph, it uses that module's name as the overall name of project and assumes that it is the only exported module; as such, it works better for programs than libraries).

Whichever way your run SourceGraph, it then creates a SourceGraph subdirectory in the same directory as the file that was passed to it, and within that subdirectory creates the analysis report in Foo.html.

SourceGraph is still experimental in terms of its ability to parse and properly understand Haskell source code and in the types of analyses it performs.

Versions [faq] 0.1, 0.2, 0.3,,,,,,,,,,,,,,,,
Change log ChangeLog
Dependencies base (>=3 && <5), Cabal (==1.6.*), containers, directory, extensible-exceptions, fgl, filepath, Graphalyze (>= && <, graphviz (>=2999.6.0.0 && <2999.7.0.0), haskell-src-exts (>=1.1.0 && <1.2.0), multiset, random [details]
License LicenseRef-GPL
Copyright (c) Ivan Lazar Miljenovic
Author Ivan Lazar Miljenovic
Category Development
Source repo head: darcs get
Uploaded by IvanMiljenovic at 2009-10-02T12:17:48Z
Distributions NixOS:
Executables SourceGraph
Downloads 21319 total (321 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs not available [build log]
All reported builds failed as of 2016-12-31 [all 7 reports]


Maintainer's Corner

For package maintainers and hackage trustees