View automerge on Snyk Open Source Advisor

Package Health Score

56 / 100

security
No known security issues
popularity
Recognized
maintenance
Inactive
community
Sustainable

Explore Similar Packages

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
2.0.0-alpha.3	\|	10/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.14.2	\|	01/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.13.0	\|	02/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.12.1	\|	08/2019	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.11.0	\|	07/2019		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

Recognized

Weekly Downloads (2,197)

GitHub Stars: 4.01K
Forks: 179
Contributors: 50

Direct Usage Popularity

The npm package automerge receives a total of 2,197 downloads a week. As such, we scored automerge popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package automerge, we found that it has been starred 4,010 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 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 is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

deprecated

Commit Frequency

Open Issues: 84
Open PR: 27
Last Release: 2 years ago
Last Commit: 16 days ago

Further analysis of the maintenance status of automerge 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 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: 7 years
Dependencies: 2 Direct
Versions: 40
Install Size: 117 kB
Dist-tags: 1
# of Files: 34
Maintainers: 4
TS Typings: Yes

automerge 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.

Not sure how to use automerge?

To help you get started, we've collected the most common ways that automerge is being used within popular public projects.

ahixon / slate-sync-bridge / test / slate / automerge.js View on Github

fixtures(__dirname, 'operations', ({ module }) => {
      const { input, output } = module
      const operations = module.default

      const inputSyncDoc = toSyncDocument(input.document.toJSON())
      const initAutomergeDoc = Automerge.init();
      const emptyAutomergeDoc = Automerge.change(initAutomergeDoc, automergeDoc => {
        automergeDoc.doc = inputSyncDoc;
      });

      const changedAutomergeDoc = Automerge.change(emptyAutomergeDoc, automergeDoc => {
        operations.forEach(op => applyOperation(automergeDoc.doc, op));
      })

      // check our rep matched
      const expectedDoc = output.document.toJSON();
      const actualDoc = toSlateDocument(changedAutomergeDoc.doc);
      assert.deepEqual(actualDoc, expectedDoc);
    })

View more ways to use automerge

automerge dependencies

automerge-wasm uuid

automerge development dependencies

@types/expect @types/mocha @types/uuid @typescript-eslint/eslint-plugin @typescript-eslint/parser eslint fast-sha256 mocha pako ts-mocha ts-node typescript

FAQs

What is automerge?

Reimplementation of `automerge` on top of the automerge-wasm backend. Visit Snyk Advisor to see a full health score report for automerge, including popularity, security, maintenance & community analysis.

Is automerge popular?

The npm package automerge receives a total of 2,197 weekly downloads. As such, automerge popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is automerge well maintained?

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

Is automerge safe to use?

The npm package automerge 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 21 November-2024, at 18:20 (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

automerge

Reimplementation of `automerge` on top of the automerge-wasm backend For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (2,197)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use automerge?

Automerge

Setup

Meta

automerge dependencies

automerge development dependencies

FAQs

What is automerge?

Is automerge popular?

Is automerge well maintained?

Is automerge safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (2,197)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use automerge?

Automerge

Setup

Meta

automerge dependencies

automerge development dependencies

FAQs

What is automerge?

Is automerge popular?

Is automerge well maintained?

Is automerge 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