[!WARNING] This is highly experimental.
This CLI is used by Avo, the Avo LSP (coming soon), and other products to do some common actions like linting the Avo configuration files.
It will show you errors that you might have missed in the Avo files along with improvements that you could make.
gem install avo-cli
avo
The linter uses different techniques to figure out if Avo configuration files are invalid or could be improved
The linter is using prism to parse the files and create an AST for each one. We the linter is run it will scan the files and return errors it found in the files.
It's doing that by scanning the AST for common patterns using user-defined rules similar to how rubocop is working.
Run bundle install to install the dependencies.
bundle
Rspec is used for tests. Run bin/rspec to run all tests.
FAQs
Unknown package
We found that avo-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
Security News
Research
Socket researchers found a malicious Maven package impersonating the legitimate ‘XZ for Java’ library, introducing a backdoor for remote code execution.