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.
superagent-as-promised
Advanced tools
npm install superagent-as-promised
var request = require('superagent');
require('superagent-as-promised')(request);
Then
request
.get('/location')
.then( function(response) {
console.log("Got "+response.text);
})
.catch( function(error) {
console.dir(error);
})
is syntactic sugar for:
var promise = request
.get('/location')
.endAsync();
promise
.then( function(response) {
console.log("Got "+response.text);
})
.catch( function(error) {
console.dir(error);
})
require('superagent-as-promised')(SuperAgent,Promise);
SuperAgent
must be a SuperAgent class; it is extended with endAsync()
, then
, and catch
methods.
The optional Promise
parameter allows you to provide your own Promise class; bluebird
is used by default.
FAQs
SuperAgent with a Promise twist
The npm package superagent-as-promised receives a total of 6,892 weekly downloads. As such, superagent-as-promised popularity was classified as popular.
We found that superagent-as-promised 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.