Cppcheck VS CoreOS Clair

Cppcheck Reviews

CoreOS Clair Reviews

Cppcheck mentions (10)

• Configuring Cppcheck, Cpplint, and JSON Lint

  I dedicated Sunday morning to going over the documentation of the linters we use in the project. The goal was to understand all options and use them in the best way for our project. Seeing their manuals side by side was nice because even very similar things are solved differently. Cppcheck is the most configurable and best documented; JSON Lint lies at the other end. - Source: dev.to / 2 months ago

• Enforcing Memory Safety?

  Using infer, someone else exploited null-dereference checks to introduce simple affine types in C++. Cppcheck also checks for null-dereferences. Unfortunately, that approach means that borrow-counting references have a larger sizeof than non-borrow counting references, so optimizing the count away potentially changes the semantics of a program which introduces a whole new way of writing subtly wrong code. Source: 11 months ago

• Static Code analysis

  For my own projects, I used cppcheck. You can check out that tool to get a feel. Depending on what industry your in, you might need to follow a standard like Misra. Source: about 1 year ago

• How do you not shoot yourself in the foot ?

  Https://cppcheck.sourceforge.io/ (there are many other static analysis tools, I just haven't used them or didn't care for them). Source: about 1 year ago

• Linting tool for prohibiting the use of specific std types

  Sounds like something that could simply be communicated with the team that writes the tests. Unless you have dozens of such classes. In that case, you could just use e.g. Cppcheck and add a rule (regular expression) that searches for usages of the forbidden classes. Source: over 1 year ago

CoreOS Clair mentions (15)

• I looked through attacks in my access logs. Here's what I found

  Besides pointing pentester tools like metasploit at yourself, there are some nice scanners out there. https://github.com/quay/clair. - Source: Hacker News / 4 months ago

• General Docker Troubleshooting, Best Practices & Where to Go From Here

  Clair. Vulnerability Static Analysis for Containers. - Source: dev.to / 4 months ago

• Open source container scanning tool to find vulnerabilities and suggest best practice improvements?

  Https://github.com/quay/clair 9.4k stars, updated 17 hours ago. Source: about 1 year ago

• Postgres: The Graph Database You Didn't Know You Had

  It scaled well compared to a naive graph abstraction implemented outside the database, but when performance wasn't great, it REALLY wasn't great. We ended up throwing it out in later versions to try and get more consistent performance. I've since worked on SpiceDB[1] which takes the traditional design approach for graph databases and simply treating Postgres as triple-store and that scales far better. IME, if you... - Source: Hacker News / about 1 year ago

• Implement DevSecOps to Secure your CI/CD pipeline

  Open source: Trivy, Gryp and Clair are widely used open source tools for container scanning. - Source: dev.to / over 1 year ago