Merge pull request #17 from sergejmueller/0.5.3

v0.5.3

CHANGELOG.md

@@ -1,3 +1,15 @@
+### v0.5.3 (2016-07-26)
+
+##### Changes
+* Core: Refactor all JS files for ES6 support
+* Core: Add `url.js` as a new `wpscan` module
+* Core: Remove `app-module-path` `npm` module
+* Core: Remove `helpers.js` `wpscan` module
+* Core: Update `request` `npm` module to v2.74.0
+* Test: Use a testcase domain
+* Readme: Text changes
+
+
 ### v0.5.2 (2016-07-22)
 
 ##### Changes

README.md

@@ -104,8 +104,8 @@ The power of `wpscan` is the flexibility: You can expand the tool functionality
   - need to be structured as follows:
 
 ```javascript
-exports.fire = function( data ) {
-  // Play with data
+exports.fire = ( data ) => {
+  // console.log( data )
 }
 ```
 
@@ -136,10 +136,5 @@ wpscan -b ~/path/to/sources.txt
 ```
 
 
-Requirements
------
-* Node.js >= 4
-
-
 Use, don't abuse!
 -----

example/rules/custom-rule.js

@@ -1,7 +1,8 @@
-'use strict';
 
-
-const log = require( 'log' );
+/**
+ * wpscan module custom-rule.js
+ * Example custom wpscan module
+ */
 
 
 /**
@@ -11,10 +12,10 @@ const log = require( 'log' );
  * @return  void
  */
 
-exports.fire = function( data ) {
+exports.fire = ( data ) => {
 
-    log.ok( 'Custom wpscan rule fired!', data.silentMode );
+    console.log( 'Custom wpscan rule fired!' )
 
-    // console.log( data );
+    console.log( data )
 
 }

index.js

@@ -1,15 +1,12 @@
 #!/usr/bin/env node
 
 
-'use strict';
-
-
 if ( ! require( 'semver' ).satisfies(
     process.versions.node,
     require( './package.json' ).engines.node
 ) ) {
-    console.error( 'Incorrect Node.js version' );
-    process.exit( 1 );
+    console.error( 'Incorrect Node.js version' )
+    process.exit( 1 )
 }
 
 
@@ -18,4 +15,4 @@ require( './lib/app' ).wpscan(
         process.argv.slice( 2 ),
         require( './config/minimist.json' )
     )
-);
+)