github-release-notes

v0.17.3

Create a release from a tag and uses issues or commits to creating the release notes. It also can generate a CHANGELOG.md file based on the release notes (or generate a brand new).

GPL-3.0
Latest version published 1 year ago
    npm install github-release-notes
  
We couldn't find any similar packages Browse all packages

Package Health Score

54 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Small

Weekly Downloads (4,951)

Download trend
Dependents
139
GitHub Stars
736
Forks
273
Contributors
30

Direct Usage Popularity

TOP 30%

The npm package github-release-notes receives a total of 4,951 downloads a week. As such, we scored github-release-notes popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package github-release-notes, we found that it has been starred 736 times, and that 139 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.

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

11/2017
12/2017
01/2018
05/2018
04/2020

Direct Vulnerabilities

0.13.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.14.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.15.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.16.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.17.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.13.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.17.3

License Risk

0.13.1
  • 0
    H
  • 0
    M
  • 0
    L
0.14.1
  • 0
    H
  • 0
    M
  • 0
    L
0.15.0
  • 0
    H
  • 0
    M
  • 0
    L
0.16.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.17.3
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
GPL-3.0
Alert

Non-Permissive License

We noticed that this project uses a license which requires less permissive conditions such as disclosing the source code, stating changes or redistributing the source under the same license. It is advised to further consult the license terms before use.


Security Policy
No

We found a way for you to contribute to the project! Looks like github-release-notes is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test github-release-notes
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

Open Issues
73
Open PR
5
Last Release
1 year ago
Last Commit
4 months ago

Further analysis of the maintenance status of github-release-notes 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 github-release-notes 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.

Community

Sustainable
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
30
Funding
No

With more than 10 contributors for the github-release-notes 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 github-release-notes is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 54/100 package health 54/100

Package

Node.js Compatibility
not defined

Age
6 years
Dependencies
19 Direct
Versions
38
Install Size
210 kB
Dist-tags
1
# of Files
24
Maintainers
1
TS Typings
No

github-release-notes 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.