It is a Code and Infrastructure (IaC) and Cloud-native Scanning/SAST/Static Analysis/Linting solution using many tools/Scanners with One Report.

You can also add any tool to it. Currently, it supports many languages and tech stacks.

If you like it, please give it a GitHub star/fork/watch/contribute. This will ensure continuous development.

Run this command in your code directory (checkout from Git – .git folder needs to be there, if you work with the normal directory, make the Git repo out of it git init && git add . && git commit etc):

sh <(curl

or for an HTML report:

sh <(curl

That’s it. You just checked your code for 2,300+ Checks (Defects, Vulnerabilities, Best Practices, Secrets – 166+ secret types) and 4,000+ YARA rules for Antidebug, Antivm, Crypto, CVE, Exploits Kits, Malware, Web shells, and APTs.

FYI Above will maintain state via (.checkmate folder). Only new commits will be checked.

Use Cases For You

This solutions should be part of DevOps/DevSecOps/Platform Engineering efforts. You can “shift left” your security efforts using below and providing tools to developers.

Asynchronous Installation Of The Whole Platform (Web Interface, Workers etc)

That way you can setup asynchronous DevSecOps feedback for the repositories you set up to scan (daily, on commit etc.)

git clone
cd betterscan-ce/dockerhub
docker compose up

Local installation On Your Laptop

Just run for CLI:

sh <(curl

or for an HTML report:

sh <(curl

It will maintain state in .checkmate folder. First run can be longer, next should be very fast. Just re-run the same command on the next iteration.

For more information click here.

Published by Tamil S

Tamil has a great interest in the fields of Cyber Security, OSINT, and CTF projects. Currently, he is deeply involved in researching and publishing various security tools with Kali Linux Tutorials, which is quite fascinating.

Leave a comment

Your email address will not be published. Required fields are marked *