Those are all very good options. If one of these is easily deployable within your organization, then you should consider converting the scripts. A single threaded Python approach was the lowest common denominator for most groups. All of the scripts have a main() function rather than a series of global statements so that they can be more easily portable to one the aforementioned options.
The optional zgrab scripts are the only utilities where Marinus performs scanning itself. The majority of information collected comes from data collected by third-parties such as Common Crawl, Censys, Rapid7 Open Data, VirusTotal, etc. Marinus is not intended to replace any network security scanner.
Marinus uses black and isort for Python code. ESLint is used for JavaScript code.
The Marinus project is continually adding new data sources.
There are no formal relationships between the third-parties and the Marinus project.
In theory, Marinus could do all of those things. When it comes to features such as alerts, everyone has different approaches (email, Slack, etc). Rather than support all of the code necessary for every possible alerting design, Marinus focuses on providing APIs for organizations to implement their own alerting according to their needs. Good apps remain focused on their core offering. Marinus' core mission is to be a database of information with an HTTPS API front end to the data.