Since the tool is making an HTTP request to CRT.sh and parsing the JSON, the description should state this instead of mentioning that the tool itself is abusing certificate transparency logs.
crt.sh is already mentioned in the README.
CT logs abuse is a concept, and that concept is the one behind this tool, regardless the API used to do that.
Since the tool is making an HTTP request to CRT.sh and parsing the JSON, the description should state this instead of mentioning that the tool itself is abusing certificate transparency logs.