hound
CodeClimate
hound | CodeClimate | |
---|---|---|
10 | 12 | |
5,573 | 2,480 | |
0.6% | 0.4% | |
4.9 | 2.4 | |
6 months ago | about 1 month ago | |
JavaScript | Ruby | |
MIT License | AGPL |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hound
-
Code Search at Google: The Story of Han-Wen and Zoekt
The same algorithm is also used in Hound (https://github.com/hound-search/hound) though I have to say the best implementation of code search by far that I've seen is https://grep.app
You really should check it out if you haven't already. It's incredibly useful; I used it all the time. Not open source though.
- Hound: Fast code searching made easy
-
Sourcegraph is no longer Open Source
There is also Hound [8].
[8]: https://github.com/hound-search/hound
-
DockerHub replacement stratagy and options
Agreed, I already have Hound setup to search across all the different repos I pull from (bitbucket, gh, gitlab, gitea etc) but now I need to find a docker equivalent.
-
Gitlab to lay off 7% of staff
i know you're looking for first-party tools that is part of the whole package, but hound does this fantastically and is extremely easy to setup, and is ridiculously fast.
-
Ask HN: How do you search large code-base before adding a feature or fixing bug?
Especially if this is long term, this is a great tool:
https://github.com/hound-search/hound#hound
It would be great if someone integrated this with tree-sitter plus something to make the search semantics a bit smarter about usages of X:
https://www.etsy.com/codeascraft/announcing-hound-a-lightnin...
Screenshots:
https://jaxenter.com/hound-go-react-code-search-engine-15008...
Another trick I use for Java: javap all the Enums out of the compiled artifacts; these indicate weird things like "modes" that you can use to start asking questions relevant to the domain. Like "why are there four ways to reprice an invoice" or finding the "types" of fees or w/e in a billing system. (assuming enum classes are used)
-
Parcel CSS: A new CSS parser, compiler, and minifier
Nice too that it's a compiled language, so you get the end tool in a nice static binary. As a non-Node dev, I hate the experience of hacking on some project and having to install a giant pool of NPM stuff just run some minifier or linter. Hound is an example of this— the guts of the project are golang, but it has a frontend that uses webpack, jest, etc: https://github.com/hound-search/hound
Which is fine, I guess; definitely use the right tool for the job. And maybe Node developers hate finding my Python projects and needing to set up a virtualenv to run them in. But all the same, I approve a direction where more of this kind of tooling is available without a build-time Node dependency.
- Grep.app: search across a half million Git repos
-
Ask HN: What are you using to introspect your code base
[2] https://about.sourcegraph.com/
[3] https://oracle.github.io/opengrok/
[4] https://github.com/hound-search/hound
CodeClimate
- Boas práticas para revisão de código
-
Top 5 AI Tools for 10x productivity
Resource Link: CodeClimate
-
How To Use Code Climate To Improve Software Quality
Want to know how to enforce allowing only high-quality software into production? Check out this post on how to use CodeClimate can help you do just that! #DevOps #SoftwareDeveloper #softwaredevelopment #SoftwareEngineering #webdevelopment #codequality
-
RFC: A Full-stack Analytics Platform Architecture
Ideally, software can quickly go from development to production. Continuous deployment and delivery are some processes that make this possible. Continuous deployment means establishing an automated pipeline from development to production while continuous delivery means maintaining the main branch in a deployable state so that a deployment can be requested at any time. Predecos uses these tools. When a commit goes into master, the code is pushed directly to the public environment. Deployment also occurs when a push is made to a development branch enabling local/e2e testing before push to master. In this manner the master branch can be kept clean and ready for deployment most of the time. Problems that surface resulting from changes are visible before reaching master. Additional automated tools are used. Docker images are built for each microservice on commit to a development or master branch, a static code analysis is performed by SonarCloud revealing quality and security problems, Snyk provides vulnerability analysis and CodeClimate provides feedback on code quality while Coveralls provides test coverage. Finally, a CircleCI build is done. Each of these components use badges which give a heads-up display of the health of the system being developed. Incorporating each of these tools into the development process will keep the code on a trajectory of stability. For example, eliminating code smells, security vulnerabilities, and broken tests before merging a pull-request (PR) into master. Using Husky on development machines to ensure that code is well linted and locally tested before it is allowed to be pushed to source-control management (SCM). Applying additional processes such as writing tests around bugs meaning reintroduction of a given bug would cause a test to fail. The automated tools would then require that test to be fixed before push to SCM meaning fewer bugs will be reintroduced. Proper development processes and automation have a strong synergy.
-
Adding coverage to CI pipeline?
The new code should not drop existing code coverage I've found in practice mainly catches changes to existing code that lack proper updates to existing tests. Our company uses Code Climate for these checks, so we don't have to manage / write our own tooling for this purpose.
-
Review Pull Requests 3x faster, ... then 10x faster
Code Climate
-
Landing my first role as a BDR in NYC.. what are some warning signs I should look for at companies?
Some exciting NYC companies tech companies I like are alloy.co, hyperscience.com, vanta.com, and codeclimate.com.
-
What you should know about JSON serialization solution in Ruby
Best code quality - Thanks to SaaS such as CodeClimate I can tell when my code quality is too low. I try to keep "code smells" absolute zero.
-
10 Signs of a good Ruby on Rails Developer
Maintainable with smaller methods, less complexity – To know more on this make a habit of using code analyzer like rubocop, Code Climate
- Any good alternative for SonarQube which is free of cost?
What are some alternatives?
opengrok - OpenGrok is a fast and usable source code search and cross reference engine, written in Java
Codacy
codesearch - Fast, indexed regexp search over large file trees
PHPStan - PHP Static Analysis Tool - discover bugs in your code without running it!
Gitlab CI - GitLab CE Mirror | Please open new issues in our issue tracker on GitLab.com
sonarqube-community-branch-plugin - A plugin that allows branch analysis and pull request decoration in the Community version of Sonarqube
septum - Context-based code search tool
dropcss - An exceptionally fast, thorough and tiny unused-CSS cleaner
HoundCI - Automated code review for GitHub pull requests.
rust-cssparser - Rust implementation of CSS Syntax Level 3
PHP Code Sniffer - PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards.