We performed a comparison between Fortify Static Code Analyzer and Mend.io based on real PeerSpot user reviews.
Find out what your peers are saying about Veracode, Checkmarx, OpenText and others in Static Code Analysis."Automating the Jenkins plugins and the build title is a big plus."
"I like the Fortify taxonomy as it provides us with a list of all of the vulnerabilities found. Fortify release updated rule packs quarterly, with accompanying documentation, that lets us know what new features are being released."
"We've found the documentation to be very good."
"It's helped us free up staff time."
"We write software, and therefore, the most valuable aspect for us is basically the code analysis part."
"The integration Subset core integration, using Jenkins is one of the good features."
"You can really see what's happening after you've developed something."
"The most valuable features include its ability to detect vulnerabilities accurately and its integration with our CI/CD pipeline."
"We find licenses together with WhiteSource which are associated with a certain library, then we get a classification of the license. This is with respect to criticality and vulnerability, so we could take action and improve some things, or replace a third-party library which seems to be too risky for us to use on legal grounds."
"We can take some measures to improve things, replace a library, or update a library which was too old or showed severe bugs."
"The overall support that we receive is pretty good. "
"The reporting capability gives us the option to generate an open-source license report in a single click, which gets all copyright and license information, including dependencies."
"We use a lot of open sources with a variety of containers, and the different open sources come with different licenses. Some come with dual licenses, some are risky and some are not. All our three use cases are equally important to us and we found WhiteSource handles them decently."
"The most valuable feature is the inventory, where it compiles a list of all of the third-party libraries that we have on our estate."
"For us, the most valuable tool was open-source licensing analysis."
"Its ease of use and good results are the most valuable."
"The product shows false positives for Python applications."
"The troubleshooting capabilities of this solution could be improved. This would reduce the number of cases that users have to submit."
"Fortify Static Code Analyzer is a good solution, but sometimes we receive false positives. If they could reduce the number of false positives it would be good."
"Fortify's software security center needs a design refresh."
"Not all languages are supported in Fortify."
"Fortify Static Code Analyzer has a bit of a learning curve, and I don't find it particularly helpful in narrowing down the vulnerabilities we should prioritize."
"It can be tricky if you want to exclude some files from scanning. For instance, if you do not want to scan and push testing files to Fortify Software Security Center, that is tricky with some IDEs, such as IntelliJ. We found that there is an Exclude feature that is not working. We reported that to them for future fixing. It needs some work on the plugins to make them consistent across IDEs and make them easier."
"It comes with a hefty licensing fee."
"If anything, I would spend more time making this more user-friendly, better documenting the CLI, and adding more examples to help expand the current documentation."
"I would like to see the static analysis included with the open-source version."
"Needs better ACL and more role definitions. This product could be used by large organisations and it definitely needs a better role/action model."
"I rated the solution an eight out of ten because WhiteSource hasn't built in a couple of features that we would have loved to use and they say they're on their roadmap. I'm hoping that they'll be able to build and deliver in 2022."
"We have ended our relationship with WhiteSource. We were using an agent that we built in the pipeline so that you can scan the projects during build time. But unfortunately, that agent didn't work at all. We have more than 500 projects, and it doubled or tripled the build time. For other projects, we had the failure of the builds without any known reason. It was not usable at all. We spent maybe one year working on the issues to try to make it work, but it didn't in the end. We should be able to integrate it with ID and Shift Left so that the developers are able to see the scan results without waiting for the build to fail."
"The only thing that I don't find support for on Mend Prioritize is C++."
"On the reporting side, they could make some improvements. They are making the reports better and better, but sometimes it takes a lot of time to generate a report for our entire organization."
"The turnaround time for upgrading databases for this tool as well as the accuracy could be improved."
Fortify Static Code Analyzer is ranked 3rd in Static Code Analysis with 14 reviews while Mend.io is ranked 4th in Software Composition Analysis (SCA) with 29 reviews. Fortify Static Code Analyzer is rated 8.4, while Mend.io is rated 8.4. The top reviewer of Fortify Static Code Analyzer writes "Seamless to integrate and identify vulnerabilities and frees up staff time". On the other hand, the top reviewer of Mend.io writes "Easy to use, great for finding vulnerabilities, and simple to set up". Fortify Static Code Analyzer is most compared with Black Duck, Snyk, Veracode, Sonatype Lifecycle and JFrog Xray, whereas Mend.io is most compared with SonarQube, Black Duck, Veracode, Snyk and Sonatype Lifecycle.
We monitor all Static Code Analysis 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.