automerge

v2.0.0-alpha.3

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

Latest version published 2 years ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

56 / 100

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.14.0 | 03/2020
Popular
  • 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
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

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 (1,206)

Download trend
GitHub Stars
3.31K
Forks
161
Contributors
40

Direct Usage Popularity

TOP 30%

The npm package automerge receives a total of 1,206 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 3,310 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
40
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

package health: 56/100 package health 56/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
73
Open PR
22
Last Release
2 years ago
Last Commit
28 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.

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.