GitHub Code Scanning vs Harness comparison

"We use GitHub Code Scanning mostly for source code management."

"It's very scalable, very easy to handle, and very intuitive."

"GitHub Code Scanning has positively impacted my organization as it helps us recognize errors and avoid many later issues which may arise."

"GitHub Code Spaces brings significant value with its simplicity and ease of use."

"The static code analysis capability in GitHub Code Scanning is a very powerful feature, providing the ability to identify vulnerabilities and ensure code quality."

"The solution helps identify vulnerabilities by understanding how ports communicate with applications running on a system. Ports are like house numbers; to visit someone's house, you must know their number. Similarly, ports are used to communicate with applications. For example, if you want to use an HTTP web server, you must use port 80. It is the port on which the web application or your server listens for incoming requests."

"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."

"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."

"It's a highly customizable DevOps tool."

"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."

"By adopting templates and various different pipelines across our own IDP platform, we have saved upwards of 30 to 40% of development time and also reduced risks of failures or error rates by upwards of 70%."

"Harness starts integrating with organizations, making everything automated without the need for manual interruption."

"Everything in Harness is configured and runs smoothly."

"Production deployments are faster and more reliable, especially for Kubernetes and cloud-based services, with significant reduction in deployment-related incidents, faster recovery when issues occur, faster, more confident releases, increased deployment frequency with higher confidence, and better governance and compliance that improved visibility and coordination across Dev, QA, Ops, and SRE teams."

"GitHub Code Scanning should add more templates."

"When running code scans, GitHub Code Scanning provides recommendations for probable fixes. However, integrating a feature where developers receive real-time highlights of vulnerabilities when checking in or merging a PR would be beneficial."

"One area for improvement could be the ability to have an AI system digest the reports generated from code scanning and provide a summary. Currently, the reports can be extensive, and users may overlook details, such as outdated libraries, which could be highlighted for attention."

"At times it becomes very annoying as it highlights certain things which are intuitive. They require code coverage for those aspects as an extra overhead."

"When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment."

"The first point for improvement is the steep learning curve, where concepts such as services, environment, pipelines, and templates take time to understand."

"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."

"I prefer the previous less compact UI version of Harness, which showed more details on the screen."

"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."

"Even with automation, there's a requirement for manual change requests for approvals."

"Infrastructure as code or pipeline as code is something that Harness severely lacks."

"Harness setup and configurations could be made easier to configure, which would be helpful."

"The minimum pricing for the tool is five dollars a month."

"GitHub Code Scanning is a moderately priced solution."