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.
memoize-resolver
Advanced tools
memoize-resolver
is a general purpose key resolver for use with a memoize
implementation like the one in Lodash.
When you memoize a function that receives multiple argments, by default only the first argument is used as the cache key.
The key resolver implemented in memoize-resolver
will create a key that's generated from all of the arguments received by the memoized function.
Install the package using NPM:
npm install memoize-resolver --save
And import the function for use with TypeScript or ES2015:
import { createResolver } from "memoize-resolver";
const work = (state, props) => { /* something expensive */ };
const resolver = createResolver();
const memoizedWork = _.memoize(work, resolver);
FAQs
A general purpose key resolver for memoize
The npm package memoize-resolver receives a total of 25,692 weekly downloads. As such, memoize-resolver popularity was classified as popular.
We found that memoize-resolver 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.