Skip to content


Repository files navigation



Nray is a free, platform and architecture independent port and application layer scanner. Apart from regular targets (list of hosts/networks), it supports dynamic target selection, based on source like certificate transparency logs or LDAP. Furthermore, nray allow to run in a distributed manner to speed up scans and to perform scans from different vantage points. Event-based results allow to further process information during the scan, e.g. using tools like jq or full-blown data analysis platforms like elasticsearch or Splunk.

This is the main repository where nray is developed. Downloads are here. If you are looking for user documentation, have a look at the project homepage. For information related to developing and contributing to nray, continue reading.

Nray is written in pure Go and its versioning follows the semantic versioning model. The development follows Vincent Driessen's "A successful git branching" model, therefore we try to keep the master branch stable and in line with releases whereas development happens on the development branch as well as branches derived from there.


Care was taken to mostly stay in line with Go's build system, meaning that the project can be built with a plain go build. Nray is written in pure Go and care was taken to select only dependencies that also fulfill this requirement, therefore a standard Go installation (plus git) is enough to build nray on and for any supported platform.

With makefile

Nevertheless, there is a makefile that is supposed to be used for building production versions (make release) - it ensures that no C dependencies are linked in and symbols are stripped from binaries to save space. Also, binaries for most common operating systems are created automatically. A call to make will build a local development version, tailored to your current OS and architecture with C libraries and Go's race detector linked in.

Without makefile

Simply run go build - in case cross compiling is desired, GOOS and GOARCH parameters control target OS and architecture. For nodes, it is possible to inject server location and port directly into the binary: go build -ldflags "-X main.server= -X main.port=8601". To get smaller binaries, strip stuff that is not necessary away via -ldflags="-s -w" when calling go build. If you need to rebuild the protobuf schemas (this is not required unless you change the wire protocol!), run make create-schemas (which requires the protobuf compiler on your system).

Docker (building)

Releases are built using the official Go Docker container. This is supposed to ensure a clean build regardless of development environment, distribution etc.

If you are unfamiliar with setting up Go or encounter any other problems, docker run --rm -v "$PWD":/nray -w /nray golang:latest make release can be used to build the release binaries in a clean environment using Docker.

Docker (running)

There are two official nray images that can be built using the Dockerfiles provided or by pulling the respective images from Docker Hub.

The first image is based on Docker's scratch image, meaning that there is no usable user space. This image is really small since it contains only nray.

The second image is based on Debian and brings some user space which makes it suitable to manually interacting with the container.

Contributing and Development

Just grab the code and fix stuff that annoys you or hack in new awesome features! Every contribution is welcome and the goal is to make nray an awesome project for users and contributors!

Your code should pass standard checks performed by go vet and go lint. I recommend using Visual Studio Code with its Go support enabled, it is a really good IDE that brings such issues up early. Nray is always developed against the latest Go release, so if you are having trouble building nray, check if you have the latest go version installed.

Creating issues

Before opening issues, please check

  • Did you read the documentation?
  • Are there already similar issues?
  • Provide as much environment information as possible: Architecture, operating system, Go version, configuration used etc.
  • Try to give steps on how to reproduce the error
  • Please use proper formatting, especially for logs (code tags). This greatly increases readability and the chance that somebody looks after your issue.

Legal stuff

Copyright 2019 by Michael Eder. Licensed under GPLv3. See LICENSE.