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.
@automerge/automerge
Advanced tools
Reimplementation of `automerge` on top of the automerge-wasm backend
Automerge is a library of data structures for building collaborative applications, this package is the javascript implementation.
Please see automerge.org for documentation.
This package is a wrapper around a core library which is written in rust and
compiled to WASM. In node
this should be transparent to you, but in the
browser you will need a bundler to include the WASM blob as part of your module
hierarchy. There are examples of doing this with common bundlers in ./examples
.
Copyright 2017–2021, the Automerge contributors. Released under the terms of the
MIT license (see LICENSE
).
FAQs
Javascript implementation of automerge, backed by @automerge/automerge-wasm
The npm package @automerge/automerge receives a total of 4,210 weekly downloads. As such, @automerge/automerge popularity was classified as popular.
We found that @automerge/automerge demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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.