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.
simpleasync
Advanced tools
Simple library to chain and run functions with asynchronous calls.
Via npm on Node:
npm install simpleasync
Reference in your program:
var async = require('simpleasync');
Define and run steps with then:
async()
.then(function (data) {
console.log(data);
return data + 1;
})
.then(function (data) {
console.log(data);
})
.run(10);
Expected output
10
11
Define and run steps with one step using a callback. Then, you can write async steps:
async()
.then(function (data, next) {
console.log(data);
next(null, data + 1); // callback(err, newdata);
})
.then(function (data) {
console.log(data);
})
.run(10);
Expected output
10
11
Use catch for catch errors:
async()
.then(function (data) {
console.log(data);
throw "Houston, we have a problem";
})
.catch(function (err) {
console.log('error:', err);
})
.run(10);
Expected output
10
error: Houston, we have a problem
Raise an error in an step with callback
async()
.then(function (data, next) {
console.log(data);
next("Houston, we have a problem", null);
})
.catch(function (err) {
console.log('error:', err);
})
.run(10);
Expected output
10
error: Houston, we have a problem
do
function generate an element of an array, to be received by the next then
or map
in sequence:
async()
.do(function (data) { return data + 1; })
.do(function (data) { return data + 2; })
.do(function (data) { return data + 3; })
.then(function (data) {
console.dir(data);
})
.run(1);
Expected output
[ 2, 3, 4 ]
map
take each element of the previous array and generate a new element
async()
.do(function (data) { return data + 1; })
.do(function (data) { return data + 2; })
.do(function (data) { return data + 3; })
.map(function (data) { return data * 3; })
.then(function (data) {
console.dir(data);
})
.run(1);
Expected output
[ 6, 9, 12 ]
do
accepts function with callback:
async()
.do(function (data, next) { next(null, data + 1); })
.do(function (data, next) { next(null, data + 2); })
.do(function (data, next) { next(null, data + 3); })
.map(function (data) { return data * 3; })
.then(function (data) {
console.dir(data);
})
.run(1);
Expected output
[ 6, 9, 12 ]
map
accepts function with callback, too:
async()
.do(function (data, next) { next(null, data + 1); })
.do(function (data, next) { next(null, data + 2); })
.do(function (data, next) { next(null, data + 3); })
.map(function (data, next) { next(null, data * data); })
.then(function (data) {
console.dir(data);
})
.run(1);
Expected output
[ 4, 9, 16 ]
git clone git://github.com/ajlopez/SimpleAsync.git
cd SimpleAsync
npm install
npm test
map
accepting async functionsTBD
MIT
Feel free to file issues and submit pull requests � contributions are welcome<
If you submit a pull request, please be sure to add or update corresponding
test cases, and ensure that npm test
continues to pass.
FAQs
Simple flow library to chain and run functions with asynchronous calls
The npm package simpleasync receives a total of 0 weekly downloads. As such, simpleasync popularity was classified as not popular.
We found that simpleasync 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.