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.
fmerge is a simple tool for merging objects. It is perfect for handling options objects.
It takes any number of parameters. It even merges recursively. Arrays will just be replaced, though.
It does require a browser that supports ES5 methods though, so for IE8 or earlier, take a look at https://github.com/olivernn/augment.js.
Installing is easy. It automatically detects the environment among the three supported types (node.js, require.js and normal browser version).
node
, simply use npm install fmerge
.require.js
-aware, so you can link it directly through require.js
as well.
require.js
version, either install through npm
or check out
from git and run node install.js
.fmerge
.var merge = require('fmerge')
console.log(merge(
{ a: 1, b: { c: 3, d: 4 }, [ 'entry', { e: 5 } ] }
, { a: 2, b: { a: 1, c: 2 }, [ 'another entry', { a: 1 } ] }
))
// { a: 2, b: { a: 1, c: 2, d: 4 }, [ 'another entry', { a: 1 } ] }
FAQs
A tool for merging objects.
We found that fmerge 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.