Horusec is an open source tool that improves identification of vulnerabilities in your project with just one command.
Check out our Documentation, you will see the complete list of tools and languages Horusec performs analysis.
You need Docker installed in your machine in order to run Horusec with all the tools we use. If you don't have Docker, we have a flag
-D truethat will disable the dependency, but it also loses much of the analysis power. We recommend using it with Docker.
If you enable commit authors
-G true, there is also a
curl -fsSL https://raw.githubusercontent.com/ZupIT/horusec/master/deployments/scripts/install.sh | bash -s latest
curl "https://github.com/ZupIT/horusec/releases/latest/download/horusec_win_x64.exe" -o "./horusec.exe" && ./horusec.exe version
You can find all binaries with versions in our releases page.
For more details on how to install, check out the documentation
To use horusec-cli and check the application's vulnerabilities, use the following command:
bash horusec start -p .
When horusec starts an analysis, it creates a folder called.horusec. This folder is the basis for not changing your code. We recommend you to add the line.horusecinto your.gitignorefile so that this folder does not need to be sent to your git server.
It is possible to use Horusec through a docker image
Run the following command to do it:
sh docker run -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd):/src horuszup/horusec-cli:latest horusec start -p /src -P $(pwd)
With the docker image we ended up having two paths where the project can be found.
-pflag will represent the project path inside the container, in our example
-Pflag will represent the project outside the container, in our example is represented by
$(pwd), will be also needed to pass the project path to mount the volume
Horusec's v1 is still available.
WARNING: The endpoint with v1 will be deprecated, please upgrade your CLI to v2. Check out more details in the documentation.
curl -fsSL https://horusec.io/bin/install.sh | bash -s latest
curl "https://horusec.io/bin/latest/win_x64/horusec.exe" -o "./horusec.exe" && ./horusec.exe version
Manage your vulnerabilities through our web interface. You can have a dashboard of metrics about your vulnerabilities, control of false positives, authorization token, update of vulnerabilities and much more. See the web application section to keep reading about it.
Check out the example below, it is sending an analysis to Horusec web services:
bash horusec start -p -a
You can analyze your project using Horusec's Visual Studio Code extension. For more information, check out the documentation.
You can perform an analysis of your project before you hold deployment in your environment by ensuring maximum security in your organization. For more information, check out the documentation:
See below: - Analyzes simultaneously 18 languages with 20 different security tools to increase accuracy; - Search for their historical git by secrets and other contents exposed; - Your analysis can be fully configurable, see all CLI available resources.
Feel free to use, recommend improvements, or contribute to new implementations.
Check out our contributing guide to learn about our development process, how to suggest bugfixes and improvements.
This is a security layer for the project and for the developers. It is mandatory.
There are two ways to use DCO, see them below:
1. Command line Follow the steps: Step 1: Check out your local git:
git config --global user.name “Name” git config --global user.email “[email protected]”
Step 2: When you commit, add the sigoff via
$ git commit -s -m "This is my commit message"
2. GitHub website
Step 1: When the commit changes box opens, add
$ git commit -m “My signed commit” Signed-off-by: usernameNote: For this option, your e-mail must be the same in registered in GitHub.
We have a project roadmap, you can come contribute with us!
Horusec also have other repositories, check out some of our other projects:
Feel free to reach out to us at:
This project exists thanks to all the contributors. You rock! ❤️ 🚀