Standard.js saw a bump from version 7.0.1 to 7.1.0 in May 2016, offering subtle but important improvements for JavaScript developers embracing the "JavaScript Standard Style." Both versions maintain the core philosophy of providing a simple, pre-defined style guide to eliminate code style debates and promote consistency across projects. The dependency on standard-engine remains consistent at version "^4.0.0", ensuring the foundational linting and formatting capabilities stay robust. Key dependencies like eslint-plugin-react, eslint-plugin-promise, eslint-config-standard, eslint-plugin-standard, and eslint-config-standard-jsx also remain at the same versions, suggesting no major shifts in React, Promise handling, or JSX rules between the two releases. The development dependencies, crucial for testing and building the package, stay unchanged.
The most notable difference lies in the eslint dependency, moving from "~2.9.0" to "~2.10.2". This incremental update to ESLint likely incorporates bug fixes, performance enhancements, and potentially new linting rules within the ESLint ecosystem. For developers, this means a slightly more refined and up-to-date linting experience. Upgrading to 7.1.0 gives you the last improvements on linting rules. Both versions are licensed under MIT. The release date of version 7.1.0 is May 17, 2016, a couple of weeks after version 7.0.1.
All the vulnerabilities related to the version 7.1.0 of the package
Prototype Pollution in Ajv
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
Improper Privilege Management in shelljs
shelljs is vulnerable to Improper Privilege Management
Improper Privilege Management in shelljs
Output from the synchronous version of shell.exec() may be visible to other users on the same system. You may be affected if you execute shell.exec() in multi-user Mac, Linux, or WSL environments, or if you execute shell.exec() as the root user.
Other shelljs functions (including the asynchronous version of shell.exec()) are not impacted.
Patched in shelljs 0.8.5
Recommended action is to upgrade to 0.8.5.
https://huntr.dev/bounties/50996581-c08e-4eed-a90e-c0bac082679c/
If you have any questions or comments about this advisory:
