npm install hell
|3||downloads in the last month|
|Version||0.1.1 last updated 3 months ago|
|Dependencies (6)||commander, esprima, estraverse, refractory, fine, super|
$ npm install hell -g
Usage: hell <path> Options: -h, --help output usage information -V, --version output the version number --ignore <path> specify path to ignore --min <number> specify min score --formatter <name> specify formatter to use --formatters display all formatters
Running the tests
$ npm test
$ npm run-script coverage
Is this tool perfect?
Can we improve it somehow?
Totally! This is just an initial implementation and I would love to hear ideas and merge pull requests in.
I have code that couldn't be detected as complex enough, but I believe it is. What do we do?
That's actually awesome! Please open a new issue with the code and explain why you think it's giving you a wrong result. From there we can start a discussion and improve the tool.
Support the author
Copyright (C) 2013 Veselin Todorov (email@example.com)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.