check-pvp

Check whether module and package imports conform to the PVP

http://www.haskell.org/haskellwiki/Import_modules_properly

Latest on Hackage:

0.0.3

This package is not currently in any snapshots. If you're interested in using it, we recommend adding it to Stackage Nightly. Doing so will make builds more reliable, and allow stackage.org to host generated Haddocks.

BSD-3-Clause licensed and maintained by Henning Thielemann

Check whether the version ranges used in the Build-Depends field matches the style of module imports according to the Package Versioning Policy (PVP). See http://www.haskell.org/haskellwiki/Package_versioning_policy. The tool essentially looks for any dependency like containers >=0.5 && <0.7 that allows the addition of identifiers to modules within the version range. Then it checks whether all module imports from containers are protected against name clashes that could be caused by addition of identifiers.

Related: There are programs that check PVP compliance of exports:

cabal-bounds: http://hackage.haskell.org/package/cabal-bounds simplifies extending the version bounds in Build-Depends fields.
precis: http://hackage.haskell.org/package/precis
apidiff: http://code.haskell.org/gtk2hs/tools/apidiff/