{"id":13724701,"date":"2020-11-30T10:31:32","date_gmt":"2020-11-30T10:31:32","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/wp-cli-10\/"},"modified":"2020-11-30T10:31:32","modified_gmt":"2020-11-30T10:31:32","slug":"wp-cli-10","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/wp-cli-10\/","title":{"rendered":"WP-CLI"},"content":{"rendered":"<p>We&#8217;d like to integrate WPScan with our internal monitoring. We could do this more easily if WPScan presented a WP-CLI command to get information.<\/p>\n<p>Ideally this command would return a short, single-line summary, such as:<\/p>\n<blockquote><p>1 critical and 3 minor vulnerabilites: Gravity Forms, Duplicate Post (2)<\/p><\/blockquote>\n<p>and an exit status of <strong>0<\/strong> for OK, <strong>1<\/strong> for minor\/warning and <strong>2<\/strong> for major\/critical. This is the Nagios\/Icinga standard for checks (see https:\/\/www.howtoforge.com\/tutorial\/write-a-custom-nagios-check-plugin\/).<\/p>\n","protected":false},"template":"","class_list":["post-13724701","topic","type-topic","status-publish","hentry","topic-tag-monitoring"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/13724701","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/13724701\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=13724701"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}