Eslint-config-strict offers a shareable ESLint configuration designed for projects requiring a high level of code quality and adherence to best practices. Versions 8.5.1 and 8.5.2, both maintained by Keith Cirkel, provide this strict linting setup, assisting developers in maintaining consistent code style and identifying potential errors early in the development process. While the core functionality remains the same, the key difference between these versions lies primarily in the release date, with version 8.5.2 released on May 20, 2016, subsequent to version 8.5.1 released on April 7, 2016.
Both versions rely on the same core dependencies: eslint for linting and eslint-plugin-filenames enhancing filename conventions. Development dependencies include tools like ghooks, semantic-release, travis-after-all, and validate-commit-msg, streamlining development workflows, automating releases and ensuring commit messages follow defined standards.
For developers, eslint-config-strict provides a standardized and robust linting foundation for your Javascript projects. Upgrading from 8.5.1 to 8.5.2 will bring you the latest, albeit minor, refinements and potentially address any underlying bug fixes or optimizations included in the newer release. The configuration itself supports a strict coding style which ultimately increases code maintainability over the course of a large, complex project. This package simplifies the process of ensuring team-wide adherence to a specific coding style promoting cleaner and more readable code.
All the vulnerabilities related to the version 8.5.2 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:
