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.
async-chain-proxy
Advanced tools
async-chain-proxy enable to call member functions by method chains.
async-chain-proxy provides method chain interfaces for accessing async methods.
class A {
async foo () {
console.log('foo')
}
async bar () {
console.log('bar')
}
}
const chainProxy = require('async-chain-proxy')
const obj = chainProxy(new A())
obj.foo().bar().end()
// output
>foo
>bar
class A {
async foo () {
return 'foo'
}
}
const chainProxy = require('async-chain-proxy')
const obj = chainProxy(new A())
obj.foo().result((v) => console.log(v)).end()
// output
>foo
This function is used for receiving result of previous action.
Indicates end of chained actions. If you didn't call end(), all the actions aren't called.
Returns target object.
FAQs
async-chain-proxy enable to call member functions by method chains.
The npm package async-chain-proxy receives a total of 1,146 weekly downloads. As such, async-chain-proxy popularity was classified as popular.
We found that async-chain-proxy 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.