Hi,
currently you are running "wpscan --update" as a post install action and if it fails, the data.zip file is extracted instead. This causes every client to download the data from our servers regardless if they use wpscan or not. We always ship a data.zip with the release containing an up to date version of the data files. Also this install mechanism reminds me a bit of the old backtrack install methods, where you need bash internet access (=set proxy vars) to update your system which is not totally clean.

I would suggest the following install method:
-) Install wpscan
-) extract data.zip into data/
-) remove data/.last_update if it exist

This would cause a prompt on the next start of wpscan if the user wants to update his data files and if the user chooses no, the extracted files are used.

This would be a great change so we can reduce the server traffic (data files are currently really big) and provide a cleaner installation method.

Thanks!
Chris