
Research
/Security News
Intercom’s npm Package Compromised in Ongoing Mini Shai-Hulud Worm Attack
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.
@prowise/eslint-config-linting-rules
Advanced tools
This repository contains the Prowise basic linting rules Rules are based on:
npm install @prowise/eslint-config-linting-rules -Deslint.config.js file in the root folder of your projectimport base from "@prowise/eslint-config-linting-rules"import typescript from "@prowise/eslint-config-linting-rules/typescript"import backend from "@prowise/eslint-config-linting-rules/backend"import frontend from "@prowise/eslint-config-linting-rules/frontend"export default frontend for a frontend project.If You want to add or overrule some settings you can add those by spreading the imported flavour and add the additions or overrides like the following examples.
NOTE: If you have a typescript project, you need to point to a tsconfig.json file which includes all the files which ESLint needs to check.
Sample of a eslint.config.js file for a backend project using node and typescript:
import backend from "@prowise/eslint-config-linting-rules/backend";
export default [
{ ignores: [ "**/reports", "**/dist/"] },
...backend,
{ languageOptions: {
parserOptions: { project: "./tsconfig.json" },
},
}];
Sample of a eslint.config.js file for a frontend project using react and typescript:
import backend from "@prowise/eslint-config-linting-rules/frontend";
export default [
{ ignores: [ "**/reports", "**/dist/"] },
...frontend,
{ languageOptions: {
parserOptions: { project: "./tsconfig.json" },
},
}];
Additional information can be found at: https://eslint.org/docs/latest/use/getting-started
ESLint version 9 comes with a nice inspector to verify your settings. It can be opened by installing it as a global node app together with eslint:
npm i -g eslint @eslint/config-inspector
After this you can run it by eslint --inspect-config
Or just run it from the command line without installing it first by npx @eslint/config-inspector
Version 2 of this library uses ESlint >= 9... This version of ESLint uses flat configuration which means that it only reads 1 configuration file in the root folder of your project.
You need to remove all .eslintrc and .eslintignore files from all sub folders and add the configuration to the main eslint.config.js file.
If you want different configuration for the different folders yo can use the following config as example:
import frontend from "@prowise/eslint-config-linting-rules/frontend";
export default [
// IGNORES MUST BE ON TOP !
{ ignores: [ "**/reports", "**/dist/"] },
...frontend,
{ languageOptions: {
parserOptions: { project: "./tsconfig.json" },
},
},
{
files: ["tests/**/*],
rules: {
jsdoc/require-jsdoc: "off",
},
},
];
As you can see, the overrides are applicable to the files given in the files attribute. When you leave it undefined it applies to all files selected by the run command.
For additional information see the official documentation on https://eslint.org/docs/latest/use/configure/migration-guide
FAQs
Default Prowise linting rules for npm packages.
The npm package @prowise/eslint-config-linting-rules receives a total of 667 weekly downloads. As such, @prowise/eslint-config-linting-rules popularity was classified as not popular.
We found that @prowise/eslint-config-linting-rules demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
/Security News
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.

Research
Socket detected a malicious supply chain attack on PyPI package lightning versions 2.6.2 and 2.6.3, which execute credential-stealing malware on import.

Research
A brand-squatted TanStack npm package used postinstall scripts to steal .env files and exfiltrate developer secrets to an attacker-controlled endpoint.