DependencyCheck VS nnn

Use Security Tools: To identify known vulnerabilities in your project's dependencies, you can utilize commands like npm audit or employ third-party security scanners such as DependencyCheck or Dependabot. These tools thoroughly analyze the dependency tree and offer actionable insights to assist you in resolving any identified vulnerabilities.

OWASP DependencyCheck - a really decent tool for scanning your project for vulnerable dependencies. It is actively developed and updated and up to date with the most latest vulnerabilities. Sometimes it can be a pain in the ass, though. Some security researchers and such find a vulnerability, publish it and the next day our CI/CD pipelines fail (the dependency check build step prevents the code from going to production). And not always there is a fix available. So, some vulnerabilities have to be ignored, temporarily. Also, to be able to ignore a vulnerability one has to do a fast risk assessment. And that will require from him to read about the vulnerability and decide if it is safe to be ignored or some different workaround must be found.

The ultimate guide somehow fails to mention the best CVE checker: https://github.com/jeremylong/DependencyCheck

We run https://github.com/jeremylong/DependencyCheck over our dependency tree regularly, via this Clojure wrapper: https://github.com/clj-holmes/clj-watson which tells us the dependency tree path to each item that has a CVE and also the version in which the CVE is addressed, if known.

We use OWASP dependency-check and pass reports to SonarQube.

From OWASP for those class of tools you could look into DependencyCheck and DependencyTrack

DependencyCheck is an open source tool that checks for vulnerabilities in dependencies used within a project. While it is a reactive tool, it's an important one since the code a developer writes is not the only code an application uses.

One more aspect to consider, although I know it is not the primary ask of the post, is to be sure and run something like dependency check on your repository. There are quite a few vulnerabilities being injected through the packaging process these days.

If you want a file full browser experience choose nnn: https://github.com/jarun/nnn . If you have a desktop file for Helix you can use the Gnome Files program to make all your programming language files open in Helix.

The other option is to just download the static version https://github.com/jarun/nnn/releases/download/v4.9/nnn-nerd-static-4.9.x86_64.tar.gz and overwrite the Debian executable at /usr/bin/nnn, but this seems a bit hacky, agreed?

You can get the 'default' nuke plugin script from https://github.com/jarun/nnn/blob/master/plugins/nuke and customize it if you need to. You define files by extension or mime type and set default and fallback apps to be opened with.

I like nnn ( n3 ).

The icon-theme seems to be driven by your terminal font as detailed in `src/icons-in-terminal.h & icons.h, and the choice of "terminal-icon vs nerd-fonts vs emoji" appear to be hard-wired at compile-time rather than at run-time.

nnn

git clone https://github.com/jarun/nnn cd nnn make O_NERD=1