inertia-clojure VS DependencyCheck

Which has first party support for Laravel and Rails, and community support for many other back ends (https://inertiajs.com/community-adapters) including an implementation for Ring middleware: https://github.com/prestancedesign/inertia-clojure

Hi, I recently developed Inertia-clojure, a Clojure adapter for Inertia to create SPA applications without writing an API.

Server-side, I wrote this following Clojure adapter (Ring middleware): https://github.com/prestancedesign/inertia-clojure

Hi everyone! I’ve written Inertia-clojure a Ring middleware for Inertia.js, a new concept to build  single-page apps without building an API. This lets you build SPA with Reagent, React, Vue and Svelte using Clojure server side for the routing, controllers with Reitit, Compojure, etc. If your interested, there is some examples in the repo: https://github.com/prestancedesign/inertia-clojure

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.