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.
This is an implementation of the Q Promise API, based on existing Promises (either native to the Browser/... or polyfilled with some other library).
It can be used to migrate from Q to native Promises or as a helper library to extend native Promises with many useful functions.
See kriskowal/q for the API reference
A few functions of the original API are not easily implementable or don't make sense for the wrapper. They should be documented here.
The code is derived from the original Q implementation, this repository is based on a fork of kriskowal/q
1.1.0
Q_DEBUG=1
.tap
method to promises, which will see a value
pass through without alteration.code === ETIMEDOUT
(Kornel Lesiński)^
version predicate
operator in any transitive dependency.Q.nextTick
.FAQs
A implementation of the Q API based on native (or polyfilled) Promises
The npm package q-vanilla receives a total of 0 weekly downloads. As such, q-vanilla popularity was classified as not popular.
We found that q-vanilla 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.