vinmap

Display Vim/Neovim's key mappings

TLDR

Perform a basic scan of a subnet

$ vinmap [[-ip|--ip_range]] [192.168.1.0/24]

Scan a domain with version and OS detection, saving results to a specific file

$ vinmap [[-ip|--ip_range]] [example.com] [[-s|--scan_type]] "-sV -O" -o [path/to/scan_results.xml]

Scan an IP range using 10 chunks and 20 concurrent threads, uses half of the system's CPU cores if not specified

$ vinmap [[-ip|--ip_range]] [10.0.0.1-10.0.0.255] [[-n|--num_chunks]] 10 [[-t|--threads]] 20

Output scan results in JSON format

$ vinmap [[-ip|--ip_range]] [192.168.1.1-192.168.1.100] [[-f|--format]] json

Scan multiple IPs with default settings and save merged XML output

$ vinmap [[-ip|--ip_range]] [192.168.1.1,192.168.1.2,...]

SYNOPSIS

No standard synopsis available as 'vinmap' is not a recognized command.

The command 'vinmap' is not recognized as a standard utility within common Linux distributions (e.g., Debian, Ubuntu, CentOS, Fedora, Arch Linux). It does not appear in typical manual pages or package repositories. It is highly probable that 'vinmap' is either a custom script or alias defined on a specific system, a typographical error in the command name, or a component of a highly specialized or obscure software package not widely distributed.

Without further context or clarification regarding its origin or purpose, it is impossible to provide a detailed analysis of its function, syntax, or parameters.

CAVEATS

Users attempting to execute 'vinmap' on a standard Linux system will most likely encounter a 'command not found' error. If 'vinmap' exists on a particular system, its functionality, options, and any associated security implications would be entirely dependent on its specific implementation, which is beyond the scope of general Linux command analysis.

HISTORY

There is no documented history of a standard 'vinmap' Linux command within widely adopted operating systems or open-source projects.