GCP CIS compliance

CIS compliance is not working for GCP

Command:
/index.js --cloud google --config ./config.js --compliance=cis

_____ _ _ _____ _ _ _
/ ____| | | |/ ____| | | (_) |
| | | | ___ _ _ __| | (___ _ __ | | ___ _| |_
| | | |/ _ \| | | |/ _` |\___ \| '_ \| |/ _ \| | __|
| |____| | (_) | |_| | (_| |____) | |_) | | (_) | | |_
\_____|_|\___/ \__,_|\__,_|_____/| .__/|_|\___/|_|\__|
| |
|_|

CloudSploit by Aqua Security, Ltd.
Cloud security auditing for AWS, Azure, GCP, Oracle, and GitHub

INFO: Using CloudSploit config file: ./config.js
INFO: Using compliance modes: cis1, cis2
INFO: Skipping AWS pagination mode
INFO: Determining API calls to make...
DEBUG: Skipping plugin Excessive Firewall Rules because it did not match compliance programs cis1, cis2
DEBUG: Skipping plugin Open Cassandra because it is not used for compliance programs
DEBUG: Skipping plugin Open DNS because it is not used for compliance programs
DEBUG: Skipping plugin Open Docker because it is not used for compliance programs
DEBUG: Skipping plugin Open SSH because it is not used for compliance programs
DEBUG: Skipping plugin Open CIFS because it is not used for compliance programs
DEBUG: Skipping plugin Open All Ports because it did not match compliance programs cis1, cis2
DEBUG: Skipping plugin Open FTP because it is not used for compliance programs
DEBUG: Skipping plugin Open Hadoop HDFS NameNode Metadata Service because it is not used for compliance programs
DEBUG: Skipping plugin Open Hadoop HDFS NameNode WebUI because it is not used for compliance programs
DEBUG: Skipping plugin Open Kibana because it is not used for compliance programs
DEBUG: Skipping plugin Open MongoDB because it is not used for compliance programs
DEBUG: Skipping plugin Open MSSQL because it is not used for compliance programs
DEBUG: Skipping plugin Open MySQL because it is not used for compliance programs
.
.
.
.
.
ERROR: Nothing to collect.
(node:237295) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)