Skip to main content

Introduction

Who we are

We are a cybersecurity company whose only purpose is to make the world a safer place.

What we do

  • We perform comprehensive security testing over all of your assets.
  • We use cutting-edge technologies and heavily trained human hackers.
  • We report vulnerabilities back to you as accurately and quickly as possible.

The source code of the technologies used is versioned in this repository and is divided across many products.

Security Rating Maintainability Rating Technical Debt Code Grade

Installing

  1. Make sure that Nix is installed on your system. If it is not, please follow this tutorial. If everything goes well, you should be able to run

    $ nix --version

    We only support versions of Nix >= 2.3 and < 2.4.

  2. Install Makes with

    $ curl -L fluidattacks.com/install/m | sh

    If everything goes well, you should be able to run

    $ m
  3. Use the products of your choice:

    $ m f /forces --help
    $ m f /melts --help
    $ m f /reviews --help
    $ m f /skims --help
    $ m f /sorts --help

Updating

No action is required on your part. Updates are automatically rolled out to your machine with a delay of at most one day. But anyway, if you want to force an update right away, just run $ rm -rf ~/.makes.

Troubleshooting

General considerations

  • A stable internet connection is required
  • A stable DNS resolver is required. Please consider using the following:
    • IPv4: 1.1.1.1, 8.8.8.8, 8.8.4.4
    • IPv6: 2001:4860:4860::8888, 2001:4860:4860::8844

Checklist

  1. If the installation failed while installing Nix,

    1. checkout the Nix manual for more detailed installation instructions, and
    2. if the problem persists, please let us know at [email protected].
  2. If the installation failed while installing Makes, please let us know at [email protected].

  3. If the process failed while using $ m gitlab:xxx /yyy,

    1. repeat the installation of Makes and try again,

    2. refresh the cache with $ rm -rf ~/.makes and try again, and

    3. if the problem persists, please let us know at [email protected].