The stability is rated an eight out of ten. 

I rate the solution a nine out of ten for stability.

The SAST component was absolutely 100% stable. The SCA product is also very extremely stable. In fact, they leverage each other in a way that it complements the overall use. It gives the user a high-level view, a 10,000-foot view with the ability to see more under a magnifying glass if you think about it from high to low.

The other components, such as IAST and the Codebashing technology, and the developer education technology, it was all integrated with radio buttons and such. I never really had any customer or client, or anyone complains, or ever come to me and say, "Hey, look, the implementation that we completed last week, it's crashed on us," or anything that would show it to be less than stable.

Have there been instances specifically where a new customer came to us and didn't have something turned on? Yes. Is there an instance where a customer might have had something configured wrong based on frequency, scanning frequency, or the depth of how deep they need to scan within the lines of code? Yes. Those were all configuration modifications that were needed. However, it was a misconception thinking that maybe it was unstable, when in fact, just a few things needed to be tweaked.

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze.

The stability of this solution depends on the size of application to be scanned, as larger files result in lower performance levels.

I rate the stability a six out of ten. We've had some stability issues, which may have been because of how we deployed the solution. When multiple scans are running in multiple applications, it closes down. This also happens where there is a large code base. After it runs for about 35 minutes, it abruptly closes. We have been discussing this issue with the Checkmarx team for it to be fixed.

Checkmarx is stable. 

When the workload contains so many source codes being scanned, and none of them present any progress, sometimes they seem to get stuck. There are also a considerable number of false positives (vulnerabilities that do not present a danger against the application or the user).

I rate the tool's stability an eight out of ten.

I would rate it as four because the scanning engine can crash sometimes.

This is a stable product.

I've run into a few bugs here and there but i would recommend installing on virtual machine and snapshoting a working install. 

The stability is great.

I rate the stability of Checkmarx a ten out of ten.

Regarding Checkmarx stability, it's an eight out of ten.

The stability of Checkmarx could improve. We're having issues with it, but we don't want to upgrade to the newest version until we make sure that the issues we're having now aren't present in the newer version.

The scan reliability sometimes is impacted and we sometimes have to restart the services to allow scans out of the queue.

The solution is stable.

Checkmarx has been stable in my usage and I'm confident to recommend it to anybody.

We've had no issues with Checkmarx's stability.

Checkmarx is a stable product, especially based on the number of updates that we receive. Every time we get a new update or a hotfix, I'm very much in the loop on getting that information. Compared to some other products, it doesn't have the churn that others do, i.e. in the number of updates and patches that we have to apply to it.

We're licensed for 100 users. Primarily we use Checkmarx for developers, managers, architects, and maybe some of the design folk, but not QA. This would solely be in the realm of development and architecture. 

There is no plan for us to increase our usage of Checkmarx. We're trying to get as many scans as possible. One of the issues that we have is the concept of an incremental scan. The more of the incremental that you do, the slower the service becomes.

When you go in and you look at the last result: it's your baseline or your full scan, followed by applying each incremental. The more of the incrementals that you have, the slower Checkmarx gets.

They've come up with a recommendation for users to do one full scan a week and maybe six incremental scans. This needs to be worked on to get the performance better on this particular tool.

We have not observed any issues, such as the application crashing, with respect to the stability of this solution.

We've had to deal with errors. When we blacklist or whitelist, we do have some issues. There are a few configuration issues. I'd rate the stability seven out of ten. It could be improved. 

The stability of Checkmarx could improve.

I would rate the stability of Checkmarx a six out of ten.

The product is stable.

I rate the product's stability a nine or ten out of ten.

Its stability is okay.

I would rate the product's stability a ten out of ten.

In general, stability is good, although sometimes it crashes. We use this product daily, and I would rate the stability a four out of five.

I've had to restart services/bounce the VM on two rare occasions.

We had no issues and it has always worked at a top level of performance.

In the latest version, the session logout doesn't work properly.

In our last update to version 8.5.0, we had a problem with DB migration but,  overall, I must say it has been stable.

The solution is very stable. There aren't bugs or glitches. The solution doesn't freeze and it's not likely to crash. We find it very reliable.

It works fine but if you have a file that is too big to scan then it takes a lot of time to run and sometimes crashes.

There is a problem with the memory, and scanning a large codebase should be done by dividing it into different files. For microservices with a small number of lines of code, it works well well. On the other hand, scanning a legacy solution such as a big monolith with millions of lines of code in it has been a problem. We need to make certain modifications to the files before we can upload them to the scan.

Maybe this issue is related to our configuration. When we have many applications to check, I need to wait a long time in the queue.

We encountered stability issues when scanning large code blocks. It consumes a lot of memory, and at times, Checkmarx services freeze and don’t work properly.

I give the stability a seven out of ten.

I have found the solution to be stable.

Checkmarx is stable. We investigate the stability of the competition as well. From my point of view, it is the best product on the market. It's relatively expensive, but it's the best product. Keep in mind, this is not my private comment. I respect the comments, results, and the statistics of Gartner and these are their findings.

This solution is stable and we have not had bugs or glitches. If it is set up according to the instructions, there will be no negative feedback from the customers.

The platform has regular updates.

It is pretty stable and we have not had any issues. We have a monitoring team that monitors the health of our infrastructure and we are alerted to any problems.

Checkmarx is stable.

Checkmarx is a good product, certainly stable.

It is pretty stable.

We did encounter stability issues. The different versions of this product provide inconsistent results when the same piece of code is scanned.

It is stable, and it works.

There were no stability issues.

We have not yet encountered any stability issues.

No issues encountered.

I have not had an issue with stability of the product.

There were no problems with stability. The application was stable in our test cases.

No issues encountered.

It has been stable during our work.

The stability is fine.

I have not encountered any stability issues.

We had to lock the number of CPUs used to not crash the Checkmarx Audit.