Lint open source repositories for common issues.
To run against a directory, add it to the command line bin/repolinter.js /my/code/dir.
To run against a git repository, use the --git option: bin/repolinter.js --git https://my.git.code/awesome.
To quickly get started, checkout this repository and run repolinter against itself.
git clone https://github.com/todogroup/repolinter
bin/repolinter.js
✔ license-file-exists: found (LICENSE)
✔ readme-file-exists: found (README.md)
✔ contributing-file-exists: found (CONTRIBUTING)
✔ readme-references-license: File README.md contains license
✔ binaries-not-present: Excluded file type doesn't exist (**/*.exe,**/*.dll)
✔ license-detectable-by-licensee: Licensee identified the license for project: Apache License 2.0
✔ test-directory-exists: found (tests)
✔ integrates-with-ci: found (.travis.yml)
✔ source-license-headers-exist: The first 5 lines of 'bin/repolinter.js' contain all of the requested patterns.
✔ package-metadata-exists: found (Gemfile)
✔ package-metadata-exists: found (package.json)
The npm log-symbols package must be installed to run repolinter.
npm install log-symbols
Repolinter will use https://github.com/benbalter/licensee and https://github.com/github/linguist when installed.
Licensee will lead to a test being done to see if the project's licensee is identified by Licensee.
Linguist allows per-language tests to be performed.
Run bundle install to get Licensee and Linguist support.
By default, results will be shown as in the example format above.
When using repolinter in another project, you can set resultFormatter to a custom formatter. Any custom formatter needs to have a format function that takes a single Result argument, and returns a string.
The default ruleset (rulesets/default.json) defines a set of common patterns against certain rules. i.e., the license-file-exists and readme-file-exists default rules both trigger a file-exists test but against different file patterns.
All languages:
- license-file-exists
- readme-file-exists
- contributing-file-exists
- code-of-conduct-file-exists
- readme-references-license
- binaries-not-present
- license-detectable-by-licensee
- test-directory-exists
- integrates-with-ci
- source-license-headers-exist
Fails if there isn't a file matching LICENSE* or COPYING* in the root of the target directory.
Fails if there isn't a file matching README* in the root of the target directory.
Fails if there isn't a file matching CONTRIB* in the root of the target directory.
Fails if there isn't a file matching CODEOFCONDUCT*, CODE-OF-CONDUCT* or CODE_OF_CONDUCT* in the root of the target directory.
Fails if the files matching README* doesn't match the regular expression license.
Fails if *.dll or *.exe files are in the target directory.
Fails if there isn't a file supporting a Continuous Integration tool, matching .gitlab-ci.yml, .travis.yml, appveyor.yml, circle.yml, or Jenkinsfile
in the root of the target directory.
Produces a failure for each file matching **/*.js,!node_modules/** option if the first 5 lines don't match all the patterns copyright, all rights reserved, and licensed under.
Fails if there isn't a directory matching test* or specs in the root of the target directory.
Currently you need to create a new ruleset to add, remove, or configure rules. We'll be adding the ability to inherit from an existing ruleset to simplify this in the future.
To override the default ruleset copy rulesets/default.json to repolint.json (or repolinter.json) in the target directory, any ancestor directory of the target directory, or your user directory.
To disable a rule change it's value to false, for example:
{
"rules": {
"all": {
"license-file-exists:file-existence": false
}
}
}
To change the level when a rule returns a failure change the first argument of the rule to error, warning, or info, for example:
{
"rules": {
"all": {
"license-detectable-by-licensee": ["info"]
}
}
}
To configure a rule's options change the second argument of the rule to an object specifying the rule's options, see rules for details about each rule's options. For example:
{
"rules": {
"all": {
"source-license-headers-exist:file-starts-with": ["warning", {"files": ["**/*.java"], "lineCount": 2, "patterns": ["Copyright", "All rights reserved", "Licensed under"]}]
}
}
}
Rules can be configured to only run if the repository contains a specific language. Languages are detected using Linguist which must be in your path, see command line dependencies for details.
The rules system is made up of rule types which can be customized to fit your needs.
Fails if none of the directories specified in the directories option exist.
Fails if the content of any of the files specified in the files option doesn't match the regular expression specified in the content option.
Fails if none of the files specified in the files option exist.
The opposite of file-contents.
Produces a failure for each file matching the files option if the first lineCount lines don't match all of the regular expressions specified in the patterns option.
Fails if any files match the type option.
Searches Git commits for configurable blacklisted words. These words can in fact be extended regular expressions. These checks can be a bit time consuming, depending on the size of the Git history.
Searches Git commit messages for configurable blacklisted words. These words can in fact be extended regular expressions. These checks can be a bit time consuming, depending on the size of the Git history.
Check for blacklisted paths in Git.
Checks whether the directory is managed with Git.
Fails if Licensee doesn't detect the repository's license.
This rule requires licensee in the path, see command line dependencies for details.
This project is licensed under the Apache 2.0 license.