Launch HN: DeepSource (YC W20) – Find and fix issues during code reviews
There&#x27;s a better solution: use open-source cli tools that do just that!<p>1. 520 Python checks? Use `wemake-python-styleguide` (wrapper around flake8) that has bigger amount of checks: <a href="https:&#x2F;&#x2F;github.com&#x2F;wemake-services&#x2F;wemake-python-styleguide" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;wemake-services&#x2F;wemake-python-styleguide</a> There&#x27;s also `pylint` with a set of awesome checks as well.<p>2. Type checking? Use `mypy`: it just a single command!<p>3. Autofixing? Use `black` &#x2F; `autopep8` &#x2F; `autoflake` and you can use `pybetter` to have the same ~15 auto-fix rules. But, it is completely free and open-source<p>I don&#x27;t like this whole idea of such tools (both technically and ethically):<p>- Why would anyone want to send all their codebase to 3rd party? We used to call it a security breach back in the days<p>- On moral side, this (and similar) projects look like thin wrappers around open-source tools but with a monetisation model. How much do these companies contribute back to the original authors of pylint, mypy, flake8? Ones who created and maintained them for years. I will be happy to be wrong here