migrate

v1.8.0

Abstract migration framework for node

MIT
Latest version published 2 months ago
    npm install migrate
  

Package Health Score

74 / 100

Security

No known security issues
Powered by Snyk
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
1.8.0 | 03/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.7.0 | 06/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.2.4 | 09/2017
Popular
  • 0
    H
  • 0
    M
  • 0
    L
0.1.6 | 10/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.5 | 11/2011
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test migrate
Get started free

Popularity

Recognized

Weekly Downloads (42,342)

Download trend
Dependents
57
GitHub Stars
1.39K
Forks
219
Contributors
40

Direct Usage Popularity

TOP 10%

The npm package migrate receives a total of 42,342 downloads a week. As such, we scored migrate popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package migrate, we found that it has been starred 1,393 times, and that 57 other projects in the ecosystem are dependent on it.

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 migrate 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 migrate is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 74/100 package health 74/100

Maintenance

Sustainable

Commit Frequency

Open Issues
17
Open PR
3
Last Release
2 months ago
Last Commit
2 months ago

Further analysis of the maintenance status of migrate based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that migrate demonstrates a positive version release cadence with at least one new version released in the past 3 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
>= 0.4.x

Age
11 years
Dependencies
8 Direct
Versions
35
Install Size
41.4 kB
Dist-tags
2
# of Files
24
Maintainers
4
TS Typings
No

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