GitHub and Klocwork both compete in the software development tools category, with GitHub having the upper hand in source code management and community features, while Klocwork stands out in static code analysis.
Features: GitHub is known for its robust source code management, community support, and seamless integration with DevOps, offering features like Git Hooks, SSH keys, and advanced security for code versioning and collaboration. Klocwork excels in static code analysis, providing valuable on-the-fly and incremental analysis to detect potential issues early, enhancing code quality.
Room for Improvement: GitHub could improve in areas like ticketing, end-to-end DevOps integration, and project management tools. Users also desire better security measures and integration with third-party platforms. Klocwork faces challenges such as false positives, limitations in language support, and complex licensing. Users request enhancements in error reporting, language support, and dashboard functionalities.
Ease of Deployment and Customer Service: GitHub operates primarily in the public cloud, offering ease of access for collaboration, with customer support relying on community forums and official documentation. Klocwork typically functions in on-premises or private cloud environments, providing comprehensive technical support through knowledgeable sales channels but with less accessibility compared to GitHub's community resources.
Pricing and ROI: GitHub features a pricing model that includes free tiers for open-source projects, offering cost benefits to smaller teams, though managing licenses becomes cumbersome as teams change size. Klocwork presents a higher-cost proposition due to its specialized static code analysis features, although its licensing models are flexible and cater to a range of organizational needs.
The main ROI factors include efficiency and how we meet compliance standards for various automotive requirements.
The technical support from GitHub is generally good, and they communicate effectively.
Some forums help you get answers faster since you just type in your concern and see resolutions from other engineers.
I have not used GitHub's technical support extensively because there are many resources and a robust knowledge base available due to the large user community.
The customer support team is very responsive, proactive, and engages in conversations to ensure our needs are met.
The issue is not about the knowledge of the support but about the prioritization of the tickets they handle.
During the initial phase, there was a need for follow-ups and clarifications.
We have never had a problem with scalability, so I would rate it at least eight to nine.
GitHub is more scalable than on-prem solutions, allowing for cloud-based scaling which is beneficial for processing large workloads efficiently.
Klocwork supports our scalability needs without issues, even as project volumes increase.
The program-to-program enablement is scalable.
If a skilled developer uses it, it is ten out of ten for stability.
It provides a reliable environment for code management.
GitHub is mostly stable, but there can be occasional hiccups.
Installation is easy, and the solution is stable.
One area for improvement in GitHub could be integration with other tools, such as test management or project management tools.
I would like to see some AI functionality included in GitHub, similar to the features seen in GitLab, to enhance productivity.
When solving merge conflicts, it would be helpful to have tooltips within the actions to know what changes could happen next when resolving a conflict.
There are too many warnings, and it requires expertise to determine the correct category for them.
Klocwork sometimes provides too many additional warnings which require expertise to manage.
We would like Klocwork to connect to Git and notify developers of issues tied to specific commits.
Normally, GitHub is not expensive, but it would be welcome if it reduces costs for developing countries.
The pricing of GitHub is reasonable, with the cost being around seven dollars per user per month for private repositories.
The pricing of GitHub depends on the choice of solutions, such as building one's own GitHub Runners to save money or using GitHub's Runners with extra costs.
It is less expensive than Coverity.
The solution is not very cheap, however, it is less expensive than Coverity.
Klocwork was competitively priced, making it a cost-effective solution for us.
The pull request facility for code review.
GitHub Actions allow for creating multiple jobs that run in different stages such as build, test, and deploy, which enable better visibility and control over the deployment pipeline.
For branching, it works well, especially in an agile environment.
The most valuable feature of Klocwork is the static analysis tools, which help identify potential security threats and errors.
Its integration with the CI/CD pipeline has helped streamline the software development process.
It takes just half a day to set up.
Klocwork detects security, safety, and reliability issues in real-time by using this static code analysis toolkit that works alongside developers, finding issues as early as possible, and integrates with teams, supporting continuous integration and actionable reporting.
We monitor all Application Security Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.