Unimus VS Cppcheck

Unimus Reviews

Cppcheck Reviews

Unimus mentions (19)

• Mixed Platform for Switches and Wireless Access Points

  I recently found out about unimus. It really works well to push configs and gather configs - you can see the changes for each config pull even across different devices. It runs as .exe or on a vm Check it out! Not even expensive - 1device 4,5€ a year or 7500€ a year unlimited. Source: 12 months ago

• Cisco Configuration Change Monitoring for Network Team

  Unimus would handle this nicely for you. It will build a versioned configuration history for your devices, and you can then see changepoints - when something changed, and what changed (including nice graphical diffs). Source: almost 1 year ago

• Track Changes on Switches/Routers/Firewalls

  Take a look at Unimus. It will generate a configuration timeline for your devices, you can generate diffs, and it will send config change notifications (including full graphical diffs in the change notification emails / Slack notifications). Also many other useful config management features in there. Source: about 1 year ago

• Version control for configs yes or no?

  I forgot also Unimus. They are amazing 🤩. https://unimus.net. Source: about 1 year ago

• What is the best way to make all cisco configs match?

  If you have zero netops experience (eg ansible) this will work: https://unimus.net/. Source: about 1 year ago

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