Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
eslint-plugin-lab
Advanced tools
Linting rules for lab testing framework
You'll first need to install ESLint:
$ npm i eslint --save-dev
Next, install eslint-plugin-lab
:
$ npm install eslint-plugin-lab --save-dev
Note: If you installed ESLint globally (using the -g
flag) then you must also install eslint-plugin-lab
globally.
Add lab
to the plugins section of your .eslintrc
configuration file. You can omit the eslint-plugin-
prefix:
{
"plugins": [
"lab"
]
}
Then configure the rules you want to use under the rules section.
{
"rules": {
"lab/no-only-experiments": "warn"
}
}
If you project follows the hapi style guide then your eslint file would look something like this:
{
"extends": "eslint-config-hapi",
"plugins": [
"lab"
],
"rules": {
"lab/no-only-experiments": "warn"
}
}
no-only-experiments
- Enforces that there are no experiment
or describe
calls marked as only()
FAQs
Linting rules for lab testing framework
We found that eslint-plugin-lab demonstrated a not healthy version release cadence and project activity because the last version was released 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.