|
1 |
| -# vulctl |
| 1 | +[](https://github.com/mchmarny/vulctl/actions/workflows/on-push.yaml) |
| 2 | +[](https://github.com/mchmarny/vulctl/actions/workflows/on-tag.yaml) |
| 3 | +[](https://codecov.io/gh/mchmarny/vulctl) |
| 4 | +[](https://github.com/mchmarny/vulctl/releases/latest) |
| 5 | +[](https://github.com/mchmarny/vulctl) |
| 6 | +[](https://goreportcard.com/report/github.com/mchmarny/vulctl) |
| 7 | + |
| 8 | +# vulctl |
2 | 9 |
|
3 | 10 | Vulnerability management tool
|
4 | 11 |
|
5 | 12 |
|
| 13 | +## CLI Installation |
| 14 | + |
| 15 | +You can install `vulctl` CLI using one of the following ways: |
| 16 | + |
| 17 | +* [Homebrew](#homebrew) |
| 18 | +* [RHEL/CentOS](#rhelcentos) |
| 19 | +* [Debian/Ubuntu](#debianubuntu) |
| 20 | +* [Go](#go) |
| 21 | +* [Binary](#binary) |
| 22 | + |
| 23 | +See the [release section](https://github.com/mchmarny/vulctl/releases/latest) for `vulctl` checksums and SBOMs. |
| 24 | + |
| 25 | +## Homebrew |
| 26 | + |
| 27 | +On Mac or Linux, you can install `vulctl` with [Homebrew](https://brew.sh/): |
| 28 | + |
| 29 | +```shell |
| 30 | +brew tap mchmarny/vulctl |
| 31 | +brew install vulctl |
| 32 | +``` |
| 33 | + |
| 34 | +New release will be automatically picked up when you run `brew upgrade` |
| 35 | + |
| 36 | +## RHEL/CentOS |
| 37 | + |
| 38 | +```shell |
| 39 | +rpm -ivh https://github.com/mchmarny/vulctl/releases/download/v$VERSION/vulctl-$VERSION_Linux-amd64.rpm |
| 40 | +``` |
| 41 | + |
| 42 | +## Debian/Ubuntu |
| 43 | + |
| 44 | +```shell |
| 45 | +wget https://github.com/aquasecurity/vulctl/releases/download/v$VERSION/vulctl-$VERSION_Linux-amd64.deb |
| 46 | +sudo dpkg -i vulctl-$VERSION_Linux-64bit.deb |
| 47 | +``` |
| 48 | + |
| 49 | +## Go |
| 50 | + |
| 51 | +If you have Go 1.17 or newer, you can install latest `vulctl` using: |
| 52 | + |
| 53 | +```shell |
| 54 | +go install github.com/mchmarny/vulctl/cmd/vulctl@latest |
| 55 | +``` |
| 56 | + |
| 57 | +## Binary |
| 58 | + |
| 59 | +You can also download the [latest release](https://github.com/mchmarny/vulctl/releases/latest) version of `vulctl` for your operating system/architecture from [here](https://github.com/mchmarny/vulctl/releases/latest). Put the binary somewhere in your $PATH, and make sure it has that executable bit. |
| 60 | + |
| 61 | +> The official `vulctl` releases include SBOMs |
| 62 | +
|
| 63 | +## Prerequisites |
| 64 | + |
| 65 | +Since you are interested in `vulctl`, you probably already have GCP account and project. If not, you learn about creating and managing projects [here](https://cloud.google.com/resource-manager/docs/creating-managing-projects). The other prerequisites include: |
| 66 | + |
| 67 | +### APIs |
| 68 | + |
| 69 | +`vulctl` also depends on a few GCP service APIs. To enable these, run: |
| 70 | + |
| 71 | +```shell |
| 72 | +gcloud services enable \ |
| 73 | + artifactregistry.googleapis.com \ |
| 74 | + containeranalysis.googleapis.com \ |
| 75 | + containerregistry.googleapis.com |
| 76 | +``` |
| 77 | + |
| 78 | +### Roles |
| 79 | + |
| 80 | +Make sure you have the following Identity and Access Management (IAM) roles in each project: |
| 81 | + |
| 82 | +> Learn how to grant multiple IAM roles to a user [here](https://cloud.google.com/iam/docs/granting-changing-revoking-access#multiple-roles) |
| 83 | +
|
| 84 | +```shell |
| 85 | +roles/containeranalysis.occurrences.editor |
| 86 | +roles/containeranalysis.notes.editor |
| 87 | +``` |
| 88 | + |
| 89 | +If you experience any issues, you can see the project level policy using following command: |
| 90 | + |
| 91 | +```shell |
| 92 | +gcloud projects get-iam-policy $PROJECT_ID --format=json > policy.json |
| 93 | +``` |
| 94 | + |
6 | 95 | ## Disclaimer
|
7 | 96 |
|
8 | 97 | This is my personal project and it does not represent my employer. While I do my best to ensure that everything works, I take no responsibility for issues caused by this code.
|
0 commit comments