lazula / mapis Goto Github PK

Collect data from multiple API endpoints in JSON format. Streamline reporting with built-in screenshot functionality.

License: GNU General Public License v3.0

Python 100.00%

mapis's Introduction

Lazula

(See below for licensing info)

Hi! I'm Lazula, sometimes LazulaTenshi. I'm a collaborator on radare2. I'm not an expert - I mostly help manage code style and quality, as well as bugfixes.

I am not a developer by trade; I am a security professional. I'm far more comfortable analyzing and breaking down existing code than creating it myself, though I'm not out of my depth creating scripts to assist in or automate common tasks. I'm most skilled in Python and C. I'm also learning some C++, and have used Lua a little bit, mostly for modding Don't Starve.

I'm trying to branch out my experience by contributing to other projects.

Certifications

OSCP
CompTIA Pentest+
CCNA
CCNA Security

My Projects

MAPIS: MAPIS (Multi-API Search) is a project I developed during my first internship at a SOC. It allows you to fetch data from multiple API endpoints, and caches all information in local JSON files with an optional disk quota.
optinit: optinit is a tool I created due to issues I encountered with Kali's livebuild toolkit. It installs a collection of public repositories and custom scripts written by me.
cryptopals: A collection of solutions for the challenges at cryptopals.com written in raw C89. The only library used is GMP for the large numbers required by asymmetric encryption.

Contributions

radare2 (My PRs): Code quality, refactoring, bugfixes. pdu command.
Greater Flavor Mod: A few bugfixes for decisions available when playing as Japan.

Licensing

The following applies only to repositories created by me. This does not apply to contributions to radare2 or other projects with specific licensing guidelines.

Most of my code is distributed under GPL3.0 ONLY. If code written by me does not have a license associated with it, assume the terms of GPL3.0 ONLY. This does not override any relevant licensing requirements.

mapis's People

Contributors

Watchers

mapis's Issues

Add ramdisk option

Ramdisk usage is already suggested, but it would be nice to integrate it into the CLI options. This should both improve performance, and more importantly, reduce disk wear.

--ramdisk: Enable caching to /dev/shm. Should warn on usage without --quota-size.
--ramdisk-keep: Don't purge the ramdisk folder after execution. Should be purged by default to keep memory usage down.

Add JSON output

Already present in the response cache, but should be available both more easily in interactive and non-interactive modes and without using the cache.

Calcify internal data structures

This project has outgrown widespread dict usage. They were very useful when this was a single-file script, but now I'm passing around dicts with expected forms, checking for key existence, using one massive dict to store everything, etc.

Normalize whitespace between outputs

Each API output should follow a standard whitespace format, e.g. 1 newline between sections and 2 trailing newlines (TBD).

Will probably happen during #9 but should be noted and tracked separately.

Add command autocompletion

Should be able to tab-complete command strings

Improve API selection options

--no-api-keys option to only use APIs which do not require a key
Aliases for APIs, short or long names. e.g. accept vt or virustotal, tc or threatcrowd

Add test suite

As the project grows, I want to ensure that changes of any size can be made without fear of breakage.

Make requests and screenshots asychronous

Should be low hanging fruit for a big performance improvement. Related to #14 as it will be part of the same system.

Add config command in interactive mode

Should be able to toggle options without closing the session

e.g:

$ python3 mapis.py -n
> config color=[on,off]
> config cache=[on,off]

Related to potential configuration changes in #4

Add configuration file

Would be a good addition. Consider:

Format: JSON, TOML, etc.
Negation options, e.g. --no-color to restore default functionality
Location: local to MAPIS, ~/.config/mapis - important for distribution as a package
Versioning and migrations

Build lookup based on required data

For example, ThreatCrowd's hash lookup only supports MD5, so if the user inputs a SHA1 hash we should check responses from other APIs to find it so we can do the TC lookup. Will need to define more info about the lookup target and populate based on viable options, then leave once all options are exhausted.