heroku-fork

v4.1.29

Heroku CLI plugin to fork an existing app into a new app.

ISC
Latest version published 4 years ago
    npm install heroku-fork
  

Package Health Score

36 / 100

Security

Security review needed
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
4.1.29 | 09/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.1 | 01/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.1.4 | 08/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.6.1 | 05/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.5.0 | 05/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
ISC
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 heroku-fork
Get started free

Popularity

Limited

Weekly Downloads (338)

Download trend
Dependents
4
GitHub Stars
44
Forks
86
Contributors
7

Direct Usage Popularity

Uncommon

The npm package heroku-fork receives a total of 338 downloads a week. As such, we scored heroku-fork popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package heroku-fork, we found that it has been starred 44 times, and that 4 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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
7
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 36/100 package health 36/100

Maintenance

Inactive
archived

Commit Frequency

Open Issues
4
Open PR
5
Last Release
4 years ago
Last Commit
3 months ago

Further analysis of the maintenance status of heroku-fork 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 heroku-fork 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.

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
not defined

Age
7 years
Dependencies
4 Direct
Versions
66
Install Size
27.3 kB
Dist-tags
1
# of Files
11
Maintainers
8
TS Typings
No

heroku-fork 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.