Skip to content

How to write an importer

Importers currently support the import of finding templates from other tools.
(In the future it might also support the import of projects.)

Copy an existing importer

You can copy, for example, the Ghostwriter plugin to .sysreptor/plugins in your home directory.

Rename the Ghostwriter directory and to the desired name. Also update the loader variable at the bottom to your new class in your .py file.

You will be able to call your plugin via reptor <plugin name in lowercase>.

In the future, we might provide an empty boilerplate for easier importer creation.

Importer settings

You will probably have to use some settings in your plugin, like from what URL the data should be fetched, or an API key. There are two options how to provide those settings:

  • CLI parameter
  • config.yaml

Settings via CLI parameter

Use the add_arguments method to add your custom CLI arguments

    def add_arguments(cls, parser, plugin_filepath=None):
        super().add_arguments(parser, plugin_filepath=plugin_filepath)
        action_group = parser.add_argument_group()
            help="API Url",

You can use --help to check if your arguments are available: reptor <your plugin name> --help.

Access your arguments via the kwargs dictionary in, e. g. self.url = kwargs.get("url", "")

Settings via config.yaml

reptor settings are managed in .sysreptor/config.yaml in your home directory. You can add plugin specific settings there, e. g.:

project_id: 42c2f73a-4383-4ec2-a3fa-281598edb0e8
token: sysreptor_TOKEN

  apikey: your_api_key
  url: http://localhost:8080

Those settings are attributes of self in your plugin. If those settings are mandatory, you can raise an exception if they are not present, e. g.:

def __init__(self, **kwargs) -> None:

    if not hasattr(self, "apikey"):
        raise ValueError(
            "API Key is required. Add to your user config."

Fetch finding templates from source

It's time to get findings from your source. Use the next_findings_batch method to yield finding template by finding template, e. g.:

def next_findings_batch(self):
    findings = self._get_findings_from_source()
    for finding_data in findings:
        yield {
            "language": "en-US",
            "status": "in-progress",
            "data": finding_data,

Note that you have to implement _get_findings_from_source yourself. This is where you access your source's API.

finding_data is a dictionary containing the fields of your source. The full data structure might look like:

    "language": "en-US",
    "status": "in-progress",
    "data": {
        "title": "Finding Title",
        "description": "Finding Description",
        "links": "\n"
The field names should be those from your source, not from SysReptor.

If your source supports translations, you can yield a list containing this data structure, e. g.

        "language": "en-US",
        "status": "in-progress",
        "data": {
            "title": "Finding Title",
            "description": "Finding Description",
            "links": "\n"

Mapping field names

Define a mapping attribute in your class to map the field names of your source to the SysReptor fields, e. g.:

    "title": "title",
    "description": "description",
    "links": "references"

In this example, the source field title maps to the SysReptor field title. However, the source field links should be mapped to the field references.

We encourage you to map to predefined SysReptor fields only. This guarantees compatibility with all SysReptor installations and designs.

Processing values

In the example above, the links field containes a newline-separated field of links. However, references in SysReptor is a list. To process and/or convert values, you can define a method called convert_<source field name>. This will be called to preprocess the values of the fields.

    def convert_links(self, value):
        return value.splitlines()

Run and enjoy

You can now run your newly created importer by reptor <your tool name>.
Use the --tags switch to add tags to imported template to be able to search for the imported templates later.