This page covers our current Roadmap for Report Ranger.
Formal release process: Breaking changes will be tagged with a major version release. Each release will be accompanied by a changelog. The latest release will be pushed to PIP.
Unit tests and better internal testing: As part of the release process we need a way to catch regressions and potential issues. This would include unit tests and test documents.
Moving vulnerabilities and appendices to the report itself: Originally the template had vulnerabilities and appendicies in-built and vulnerabilities will automatically be processed and included. This is all being brought into the report file itself by default. Although it will still be possible to have a template with content in it, this will no longer be default or by design.
Soft coded importing of vulnerabilities: The vulnerabilities will be moved into an import in the following format:
import:
vulnerabilities:
jumpbox_vulnerabilities:
directory: jumpbox_vulnerabilities
This means that vulnerabilities will no longer be hardcoded in a report in any way.
Improved documentation: A full function reference will be documented in the Wiki. This will include all functions as well as a descriptions of the functions themselves and their parameters.
Additional changes:
- Include better cross referencing
- Simplify the default latex template
- Have a more formal way of using macros and default content included in the template
- Soft code a template mapper so that you can just include a single file which references all potential templates