automerge-backend-wasm

v0.1.4

A js/wasm wrapper for the rust implementation of automerge-backend For more information about how to use this package see README

Latest version published 4 years ago

License: MIT

NPM

GitHub

Package Health Score

58 / 100

security
No known security issues
popularity
Small
maintenance
Inactive
community
Sustainable

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
0.1.4	\|	02/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Small

Weekly Downloads (0)

GitHub Stars: 4.04K
Forks: 179
Contributors: 50

Direct Usage Popularity

The npm package automerge-backend-wasm receives a total of 0 downloads a week. As such, we scored automerge-backend-wasm popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package automerge-backend-wasm, we found that it has been starred 4,035 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 50
Funding: No

With more than 10 contributors for the automerge-backend-wasm repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like automerge-backend-wasm is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 84
Open PR: 26
Last Release: 4 years ago
Last Commit: 1 month ago

Further analysis of the maintenance status of automerge-backend-wasm based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for automerge-backend-wasm is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 5 years
Dependencies: 0 Direct
Versions: 3
Install Size: 1.14 MB
Dist-tags: 1
# of Files: 9
Maintainers: 1
TS Typings: No

automerge-backend-wasm has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

automerge-backend-wasm

This is a wrapper for the rust implementation of automerge-backend to be used with Automerge.

Using

You can require this syncronously as a CommonJS module or import it as a ES6 module

let Automerge = require("automerge")
let Backend = require("automerge-backend-wasm")
Automerge.setDefaultBackend(Backend)

import * as Automerge from "automerge"
import * as Backend from "automerge-backend-wasm"
Automerge.setDefaultBackend(Backend)

Note that the first uses a syncronous filesystem load of the wasm and will not be transferable to a browser bundle. The second uses ES6 wasm import statements which should work in all modern browsers but require a '--experimental-wasm-modules' flag on nodejs (v13 on) unless you pack/bundle the code into compatible format.

FAQs

What is automerge-backend-wasm?

A js/wasm wrapper for the rust implementation of automerge-backend. Visit Snyk Advisor to see a full health score report for automerge-backend-wasm, including popularity, security, maintenance & community analysis.

Is automerge-backend-wasm popular?

We’re still processing downloads data for the npm package automerge-backend-wasm. Visit the popularity section on Snyk Advisor to see the full popularity analysis.

Is automerge-backend-wasm well maintained?

We found indications that automerge-backend-wasm is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is automerge-backend-wasm safe to use?

The npm package automerge-backend-wasm was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 3 December-2024, at 09:43 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (0)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

automerge-backend-wasm

Using

FAQs

What is automerge-backend-wasm?

Is automerge-backend-wasm popular?

Is automerge-backend-wasm well maintained?

Is automerge-backend-wasm safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues