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-require-in-package
Advanced tools
ESLint rule that validates ES6 imports are defined in local package.json
ES6 import only.
Given this:
import * as a from 'b';
import c from 'd';
import {e as f} from 'g';
import recast from 'recast';
import h from './i';
It will check dependencies, devDependencies, and peerDependencies for the existance of b, d, g, and recast. If they are not found, this message will print:
1:1 error `b` : is not a dependency in the local package.json require-in-package
npm install eslint-plugin-require-in-package
.eslintrc
{
"parser": "babel-eslint",
"env": {
"node": true,
"es6": true,
"mocha": true
},
"ecmaFeatures": {
"modules": true
},
"plugins": ["require-in-package"],
// 0 - turn rule off
// 1 - rule generates warnings
// 2 - rule generates errors
"rules": {
"require-in-package/require-in-package": 2
}
}
FAQs
ESLint rule that validates ES6 imports are defined in local package.json
We found that eslint-plugin-require-in-package 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.