Lintspec is a command-line utility (linter) that checks the completeness and validity of NatSpec doc-comments in Solidity code. It is focused on speed and ergonomics. By default, lintspec will respect gitignore rules when looking for Solidity source files.
Dual-licensed under MIT or Apache 2.0.
Note: the
main
branch can contain unreleased changes. To view the README information for the latest stable release, visit crates.io or select the latest git tag from the branch/tag dropdown.
cargo install lintspec
Via cargo-binstall
cargo binstall lintspec
nix-env -iA nixpkgs.lintspec
# or
nix-shell -p lintspec
# or
nix run nixpkgs#lintspec
Head over to the releases page!
Usage: lintspec [OPTIONS] [PATH]... [COMMAND]
Commands:
init Create a `.lintspec.toml` config file with default values
help Print this message or the help of the given subcommand(s)
Arguments:
[PATH]... One or more paths to files and folders to analyze
Options:
-e, --exclude <EXCLUDE> Path to a file or folder to exclude (can be used more than once)
-o, --out <OUT> Write output to a file instead of stderr
--inheritdoc Enforce that all public and external items have `@inheritdoc`
--notice-or-dev Do not distinguish between `@notice` and `@dev` when considering "required" validation rules
--notice-ignored <TYPE> Ignore `@notice` for these items (can be used more than once)
--notice-required <TYPE> Enforce `@notice` for these items (can be used more than once)
--notice-forbidden <TYPE> Forbid `@notice` for these items (can be used more than once)
--dev-ignored <TYPE> Ignore `@dev` for these items (can be used more than once)
--dev-required <TYPE> Enforce `@dev` for these items (can be used more than once)
--dev-forbidden <TYPE> Forbid `@dev` for these items (can be used more than once)
--param-ignored <TYPE> Ignore `@param` for these items (can be used more than once)
--param-required <TYPE> Enforce `@param` for these items (can be used more than once)
--param-forbidden <TYPE> Forbid `@param` for these items (can be used more than once)
--return-ignored <TYPE> Ignore `@return` for these items (can be used more than once)
--return-required <TYPE> Enforce `@return` for these items (can be used more than once)
--return-forbidden <TYPE> Forbid `@return` for these items (can be used more than once)
--json Output diagnostics in JSON format
--compact Compact output
--sort Sort the results by file path
-h, --help Print help (see more with '--help')
-V, --version Print version
Create a default configuration with the following command:
lintspec init
This will create a .lintspec.toml
file with the default configuration in the current directory.
Environment variables (in capitals, with the LS_
prefix) can also be used and take precedence over the
configuration file. They use the same names as in the TOML config file and use the _
character as delimiter for
nested items.
Examples:
LS_LINTSPEC_PATHS=[src,test]
LS_LINTSPEC_INHERITDOC=false
LS_LINTSPEC_NOTICE_OR_DEV=true
: if the setting name contains_
, it is not considered a delimiterLS_OUTPUT_JSON=true
LS_CONSTRUCTOR_NOTICE=required
Finally, the tool can be customized with command-line arguments, which take precedence over the other two methods. To see the CLI usage information, run:
lintspec help
You can check your code in CI with the lintspec GitHub Action. Any .lintspec.toml
or .nsignore
file in the
repository's root will be used to configure the execution.
The action generates annotations that are displayed in the source files when viewed (e.g. in a PR's "Files" tab).
The following options are available for the action (all are optional if a config file is present):
Input | Default Value | Description | Example |
---|---|---|---|
working-directory |
"./" |
Working directory path | "./src" |
paths |
"[]" |
Paths to scan, relative to the working directory, in square brackets and separated by commas. Required unless a .lintspec.toml file is present in the working directory. |
"[path/to/file.sol,test/test.sol]" |
exclude |
"[]" |
Paths to exclude, relative to the working directory, in square brackets and separated by commas | "[path/to/exclude,other/path.sol]" |
extra-args |
Extra arguments passed to the lintspec command |
"--constructor=true" |
|
version |
"latest" |
Version of lintspec to use. For enhanced security, you can pin this to a fixed version | "0.1.5" |
fail-on-problem |
"true" |
Whether the action should fail when NatSpec problems have been found. Disabling this only creates annotations for found problems, but succeeds |
"false" |
name: Lintspec
on:
pull_request:
jobs:
lintspec:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: beeb/lintspec@main
# all the lines below are optional
with:
working-directory: "./"
paths: "[]"
exclude: "[]"
extra-args: ""
version: "latest"
fail-on-problem: "true"
This tool walks in the footsteps of natspec-smells, thanks to them for inspiring this project!
On an AMD Ryzen 9 7950X processor with 64GB of RAM, linting the
Uniswap/v4-core src
folder on WSL2 (Ubuntu), lintspec is about 214x faster, or
0.46% of the execution time:
Benchmark 1: npx @defi-wonderland/natspec-smells --include "src/**/*.sol"
Time (mean Β± Ο): 12.484 s Β± 0.157 s [User: 13.581 s, System: 0.594 s]
Range (min β¦ max): 12.288 s β¦ 12.817 s 10 runs
Warning: Ignoring non-zero exit code.
Benchmark 2: lintspec src --compact=true
Time (mean Β± Ο): 58.2 ms Β± 1.3 ms [User: 264.0 ms, System: 67.9 ms]
Range (min β¦ max): 53.9 ms β¦ 61.3 ms 50 runs
Warning: Ignoring non-zero exit code.
Summary
lintspec src --compact=true ran
214.55 Β± 5.61 times faster than npx @defi-wonderland/natspec-smells --include "src/**/*.sol"
Feature | lintspec |
natspec-smells |
---|---|---|
Identify missing NatSpec | β | β |
Identify duplicate NatSpec | β | β |
Include files/folders | β | β |
Exclude files/folders | β | β |
Enforce usage of @inheritdoc |
β | β |
Enforce NatSpec on constructors | β | β |
Configure via config file | β | β |
Configure via env variables | β | β |
Respects gitignore files | β | β |
Granular validation rules | β | β |
Pretty output with code excerpt | β | β |
JSON output | β | β |
Output to file | β | β |
Multithreaded | β | β |
No pre-requisites (node/npm) | β | β |