Gathering detailed insights and metrics for @silvapav/github-release-notes
Gathering detailed insights and metrics for @silvapav/github-release-notes
Gathering detailed insights and metrics for @silvapav/github-release-notes
Gathering detailed insights and metrics for @silvapav/github-release-notes
Node module to create a release or a changelog from a tag and uses issues or commits to creating the release notes.
npm install @silvapav/github-release-notes
Typescript
Module System
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GPL-3.0 License
888 Stars
282 Commits
319 Forks
12 Watchers
10 Branches
32 Contributors
Updated on Jul 17, 2025
Latest Version
0.9.15
Package Id
@silvapav/github-release-notes@0.9.15
Unpacked Size
63.80 kB
Size
12.32 kB
File Count
14
NPM Version
6.9.0
Node Version
8.9.1
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Node module that generates release notes based on commit messages or closed issues between tags. It also can create a full changelog or add the latest release notes to the existing changelog file.
If you want to include it in a task, you can use grunt-github-release-notes
Install github-release-notes
via npm:
1npm install github-release-notes -g
First generate a github token
at this link. You only need "repo" scope.
Then add this to ~/.bash_profile
or ~/.zshrc
):
1export GREN_GITHUB_TOKEN=your_token_here
1# Navigate to your project directory 2cd ~/Path/to/repo 3# Run the task 4gren
Otherwise, you can run it anywhere passing the repo information:
1gren --username=[username] --repo=[repo name]
To use a specific token you can specify it as option:
1gren --token=[your token]
Gren has two main usages: release
and changelog
.
You can select the action with the --action
option.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 8/11 approved changesets -- score normalized to 7
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
79 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-14
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More