Themis VS snyk

Now, the real world work starts. We introduce interns to the world of popular cryptographic libraries, help them to make their first OSS contributions, and let them practice with our cryptographic library Themis which provides a high-level crypto API on 14 languages.

There are a number of ways that you can install the Snyk CLI on your machine, ranging from using the available stand-alone executables to using package managers such as Homebrew for macOS and Scoop for Windows.

There's tons of tools to solve each of these problems Snyk for vulnerability scanning, tons of license checker plugins (like we use license-webpack-plugin which generates the license text for everything we distribute and fails a build if a license doesn't have one of our allowlisted licenses.

Snyk provides security score and vulnerability count badges, which you can link to the relevant pages, as in these examples:

Note: I remind you that we support multiple strategy for vulnerabilities like Sonatype or Snyk.

Ideally, software can quickly go from development to production. Continuous deployment and delivery are some processes that make this possible. Continuous deployment means establishing an automated pipeline from development to production while continuous delivery means maintaining the main branch in a deployable state so that a deployment can be requested at any time. Predecos uses these tools. When a commit goes into master, the code is pushed directly to the public environment. Deployment also occurs when a push is made to a development branch enabling local/e2e testing before push to master. In this manner the master branch can be kept clean and ready for deployment most of the time. Problems that surface resulting from changes are visible before reaching master. Additional automated tools are used. Docker images are built for each microservice on commit to a development or master branch, a static code analysis is performed by SonarCloud revealing quality and security problems, Snyk provides vulnerability analysis and CodeClimate provides feedback on code quality while Coveralls provides test coverage. Finally, a CircleCI build is done. Each of these components use badges which give a heads-up display of the health of the system being developed. Incorporating each of these tools into the development process will keep the code on a trajectory of stability. For example, eliminating code smells, security vulnerabilities, and broken tests before merging a pull-request (PR) into master. Using Husky on development machines to ensure that code is well linted and locally tested before it is allowed to be pushed to source-control management (SCM). Applying additional processes such as writing tests around bugs meaning reintroduction of a given bug would cause a test to fail. The automated tools would then require that test to be fixed before push to SCM meaning fewer bugs will be reintroduced. Proper development processes and automation have a strong synergy.

Security integrations: Use tools like Snyk to monitor your application dependencies for vulnerabilities.

I didn't research in details how Snyk detects potential issues but using the Snyk VSCode extension did not report any vulnerabilities either.

Normally you scan the images for vulns not the host filesystem. What are you using to scan for vulns? You might want to try something like https://snyk.io/ or https://aquasecurity.github.io/trivy/v0.27.1/

Snyk: Scan your dependencies (SCA - Software Component Analysis)The libraries and packages you use often end up containing vulnerabilities. Tools like Snyk can scan your dependencies and tell you which to update for security reasons.