GitHub and Klocwork are prominent in software development, competing in code management and static analysis, respectively. GitHub appears to have an edge in collaborative features and code management, while Klocwork excels in code vulnerability detection in safety-critical environments.
Features: GitHub's valuable features include extensive code management capabilities such as Git Hooks, SSH keys, and seamless integrations with tools like Jira. It also offers scalability, user-friendly operations, and robust security. Klocwork provides static code analysis, incremental analysis, and language support for mission-critical applications, benefiting developers focused on secure code.
Room for Improvement: GitHub could improve by enhancing large file uploads, Slack integration, and addressing multilingual issues. It faces challenges in project management and needs better LDAP and automation tool syncing. Klocwork could reduce false positives and improve language support, custom checker integration, and its dashboard experience.
Ease of Deployment and Customer Service: GitHub offers flexibility with public and hybrid cloud deployments, supported by a vast community network and extensive documentation. However, its technical support can be inconsistent. Klocwork is mainly deployed on-premises or in private cloud environments, enjoying satisfactory customer support despite some licensing challenges.
Pricing and ROI: GitHub's cost-effectiveness comes from its open-source nature, offering free options alongside various licensing models which could complicate tracking. Klocwork, though expensive, provides significant value in security environments with pricing models suited to organizational needs. Its ROI is favorable due to its contribution to code quality.
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.
