GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.

Issues (1881)

Security Analysis    not enabled

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  Cross-Site Scripting
Cross-Site Scripting enables an attacker to inject code into the response of a web-request that is viewed by other users. It can for example be used to bypass access controls, or even to take over other users' accounts.
  File Exposure
File Exposure allows an attacker to gain access to local files that he should not be able to access. These files can for example include database credentials, or other configuration files.
  File Manipulation
File Manipulation enables an attacker to write custom data to files. This potentially leads to injection of arbitrary code on the server.
  Object Injection
Object Injection enables an attacker to inject an object into PHP code, and can lead to arbitrary code execution, file exposure, or file manipulation attacks.
  Code Injection
Code Injection enables an attacker to execute arbitrary code on the server.
  Response Splitting
Response Splitting can be used to send arbitrary responses.
  File Inclusion
File Inclusion enables an attacker to inject custom files into PHP's file loading mechanism, either explicitly passed to include, or for example via PHP's auto-loading mechanism.
  Command Injection
Command Injection enables an attacker to inject a shell command that is execute with the privileges of the web-server. This can be used to expose sensitive data, or gain access of your server.
  SQL Injection
SQL Injection enables an attacker to execute arbitrary SQL code on your database server gaining access to user data, or manipulating user data.
  XPath Injection
XPath Injection enables an attacker to modify the parts of XML document that are read. If that XML document is for example used for authentication, this can lead to further vulnerabilities similar to SQL Injection.
  LDAP Injection
LDAP Injection enables an attacker to inject LDAP statements potentially granting permission to run unauthorized queries, or modify content inside the LDAP tree.
  Header Injection
  Other Vulnerability
This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.
  Regex Injection
Regex Injection enables an attacker to execute arbitrary code in your PHP process.
  XML Injection
XML Injection enables an attacker to read files on your local filesystem including configuration files, or can be abused to freeze your web-server process.
  Variable Injection
Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.
Unfortunately, the security analysis is currently not available for your project. If you are a non-commercial open-source project, please contact support to gain access.

gutenberg/scripts/start.js (51 issues)

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

1
/**
2
 * Start
3
 *
4
 * The create-guten-block CLI starts here.
5
 *
6
 * TODO:
7
 *  - checkRequiredFiles
8
 *  - printBuildError
9
 */
10
'use strict';
0 ignored issues
show
Use the function form of "use strict".
Loading history...
11
12
// Do this as the first thing so that any code reading it knows the right env.
13
process.env.BABEL_ENV = 'development';
0 ignored issues
show
process does not seem to be defined.
Loading history...
14
process.env.NODE_ENV = 'development';
0 ignored issues
show
process does not seem to be defined.
Loading history...
15
16
// Makes the script crash on unhandled rejections instead of silently
17
// ignoring them. In the future, promise rejections that are not handled will
18
// terminate the Node.js process with a non-zero exit code.
19
process.on( 'unhandledRejection', err => {
0 ignored issues
show
'arrow function syntax (=>)' is only available in ES6 (use 'esversion: 6').

Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code.

Further Reading:

Loading history...
process does not seem to be defined.
Loading history...
20
	throw err;
21
} );
22
23
const ora = require( 'ora' );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
require does not seem to be defined.
Loading history...
24
const chalk = require( 'chalk' );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
require does not seem to be defined.
Loading history...
25
const webpack = require( 'webpack' );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
require does not seem to be defined.
Loading history...
26
const config = require( '../config/webpack.config.dev' );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
require does not seem to be defined.
Loading history...
27
const resolvePkg = require( 'resolve-pkg' );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
require does not seem to be defined.
Loading history...
28
const cgbDevUtilsPath = resolvePkg( 'cgb-dev-utils', { cwd: __dirname } );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
__dirname does not seem to be defined.
Loading history...
29
const clearConsole = require( cgbDevUtilsPath + '/clearConsole' );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
require does not seem to be defined.
Loading history...
30
const formatWebpackMessages = require( cgbDevUtilsPath +
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
require does not seem to be defined.
Loading history...
31
	'/formatWebpackMessages' );
32
33
// Don't run below node 8.
34
const currentNodeVersion = process.versions.node;
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
process does not seem to be defined.
Loading history...
35
const semver = currentNodeVersion.split( '.' );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
36
const major = semver[ 0 ];
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
37
38
// If below Node 8.
39
if ( major < 8 ) {
40
	console.error(
0 ignored issues
show
console does not seem to be defined.
Loading history...
41
		chalk.red(
42
			'You are running Node ' +
43
				currentNodeVersion +
44
				'.\n' +
45
				'Create Guten Block requires Node 8 or higher. \n' +
46
				'Kindly, update your version of Node.'
47
		)
48
	);
49
	process.exit( 1 );
0 ignored issues
show
process does not seem to be defined.
Loading history...
50
}
51
52
clearConsole();
53
54
// Init the spinner.
55
const spinner = new ora( { text: '' } );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
56
57
// Create the production build and print the deployment instructions.
58
async function build( webpackConfig ) {
0 ignored issues
show
Did you forget to assign or call a function?

This error message can for example pop up if you forget to assign the result of a function call to a variable or pass it to another function:

function someFunction(x) {
    (x > 0) ? callFoo() : callBar();
}

// JSHint expects you to assign the result to a variable:
function someFunction(x) {
    var rs = (x > 0) ? callFoo() : callBar();
}

// If you do not use the result, you could also use if statements in the
// case above.
function someFunction(x) {
    if (x > 0) {
        callFoo();
    } else {
        callBar();
    }
}
Loading history...
Missing semicolon.
Loading history...
async does not seem to be defined.
Loading history...
There were too many errors found in this file; checking aborted after 45%.

If JSHint finds too many errors in a file, it aborts checking altogether because it suspects a configuration issue.

Further Reading:

Loading history...
59
	// Compiler Instance.
60
	const compiler = await webpack( webpackConfig );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
Missing semicolon.
Loading history...
61
62
	// Run the compiler.
63
	compiler.watch( {}, ( err, stats ) => {
0 ignored issues
show
'arrow function syntax (=>)' is only available in ES6 (use 'esversion: 6').

Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code.

Further Reading:

Loading history...
64
		clearConsole();
65
66
		if ( err ) {
67
			return console.log( err );
0 ignored issues
show
console does not seem to be defined.
Loading history...
68
		}
69
70
		// Get the messages formatted.
71
		const messages = formatWebpackMessages( stats.toJson( {}, true ) );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
72
73
		// If there are errors just show the errors.
74
		if ( messages.errors.length ) {
75
			// Only keep the first error. Others are often indicative
76
			// of the same problem, but confuse the reader with noise.
77
			if ( messages.errors.length > 1 ) {
78
				messages.errors.length = 1;
79
			}
80
81
			// Clear success messages.
82
			clearConsole();
83
84
			// Formatted errors.
85
			console.log( '\n❌ ', chalk.black.bgRed( ' Failed to compile. \n' ) );
0 ignored issues
show
console does not seem to be defined.
Loading history...
86
			const logErrors = console.log( '\n👉 ', messages.errors.join( '\n\n' ) );
0 ignored issues
show
Backwards Compatibility introduced by
'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).
Loading history...
console does not seem to be defined.
Loading history...
87
			console.log( '\n' );
0 ignored issues
show
console does not seem to be defined.
Loading history...
88
			spinner.start(
89
				chalk.dim(
90
					'Watching for changes... let\'s fix this... (Press CTRL + C to stop).'
91
				)
92
			);
93
			return logErrors;
94
		}
95
96
		// CI.
97
		if (
98
			process.env.CI &&
0 ignored issues
show
process does not seem to be defined.
Loading history...
99
			( typeof process.env.CI !== 'string' ||
0 ignored issues
show
process does not seem to be defined.
Loading history...
100
				process.env.CI.toLowerCase() !== 'false' ) &&
0 ignored issues
show
process does not seem to be defined.
Loading history...
101
			messages.warnings.length
102
		) {
103
			console.log(
0 ignored issues
show
console does not seem to be defined.
Loading history...
104
				chalk.yellow(
105
					'\nTreating warnings as errors because process.env.CI = true.\n' +
106
						'Most CI servers set it automatically.\n'
107
				)
108
			);
109
			return console.log( messages.warnings.join( '\n\n' ) );
0 ignored issues
show
console does not seem to be defined.
Loading history...
110
		}
111
112
		// Start the build.
113
		console.log( `\n${ chalk.dim( 'Let\'s build and compile the files...' ) }` );
0 ignored issues
show
'template literal syntax' is only available in ES6 (use 'esversion: 6').

Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code.

Further Reading:

Loading history...
console does not seem to be defined.
Loading history...
114
		console.log( '\n✅ ', chalk.black.bgGreen( ' Compiled successfully! \n' ) );
0 ignored issues
show
console does not seem to be defined.
Loading history...
115
		console.log(
0 ignored issues
show
console does not seem to be defined.
Loading history...
116
			chalk.dim( '   Note that the development build is not optimized. \n' ),
117
			chalk.dim( '  To create a production build, use' ),
118
			chalk.green( 'npm' ),
119
			chalk.white( 'run build\n' )
120
		);
121
		return spinner.start(
122
			`${ chalk.dim( 'Watching for changes... (Press CTRL + C to stop).' ) }`
0 ignored issues
show
'template literal syntax' is only available in ES6 (use 'esversion: 6').

Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code.

Further Reading:

Loading history...
123
		);
124
	} );
125
}
126
127
build( config );
128