Gathering detailed insights and metrics for conventional-changelog-angular
Gathering detailed insights and metrics for conventional-changelog-angular
Gathering detailed insights and metrics for conventional-changelog-angular
Gathering detailed insights and metrics for conventional-changelog-angular
@commitlint/config-conventional
Shareable commitlint config enforcing conventional commits
standard-version
replacement for `npm version` with automatic CHANGELOG generation
@commitlint/config-angular
Shareable commitlint config enforcing the angular commit convention
conventional-changelog-custom-config
This preset extends the angular preset
Generate changelogs and release notes from a project's commit messages and metadata.
npm install conventional-changelog-angular
Typescript
Module System
Min. Node Version
Node Version
NPM Version
99.7
Supply Chain
100
Quality
81.5
Maintenance
100
Vulnerability
100
License
conventional-changelog: v7.1.1
Updated on Jul 10, 2025
conventional-changelog-conventionalcommits: v9.1.0
Updated on Jul 10, 2025
conventional-changelog-writer: v8.2.0
Updated on Jul 09, 2025
conventional-commits-parser: v6.2.0
Updated on Jun 09, 2025
conventional-recommended-bump: v11.2.0
Updated on Jun 07, 2025
conventional-changelog: v7.1.0
Updated on Jun 07, 2025
TypeScript (77.48%)
JavaScript (20.23%)
Handlebars (2.29%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
ISC License
8,156 Stars
1,786 Commits
729 Forks
54 Watchers
3 Branches
152 Contributors
Updated on Jul 11, 2025
Latest Version
8.0.0
Package Id
conventional-changelog-angular@8.0.0
Unpacked Size
12.80 kB
Size
4.78 kB
File Count
11
NPM Version
10.5.0
Node Version
18.20.2
Published on
May 03, 2024
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
1
conventional-changelog angular preset.
Issues with the convention itself should be reported on the Angular issue tracker.
1# yarn 2yarn add -D conventional-changelog-angular 3# pnpm 4pnpm add -D conventional-changelog-angular 5# npm 6npm i -D conventional-changelog-angular
Angular's commit message guidelines.
Appears under "Features" header, pencil subheader:
feat(pencil): add 'graphiteWidth' option
Appears under "Bug Fixes" header, graphite subheader, with a link to issue #28:
fix(graphite): stop graphite breaking when width < 0.1
Closes #28
Appears under "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation:
perf(pencil): remove graphiteWidth option
BREAKING CHANGE: The graphiteWidth option has been removed. The default graphite width of 10mm is always used for performance reason.
The following commit and commit 667ecc1
do not appear in the changelog if they are under the same release. If not, the revert commit appears under the "Reverts" header.
revert: feat(pencil): add 'graphiteWidth' option
This reverts commit 667ecc1654a317a13331b17617d973392f415f02.
A commit message consists of a header, body and footer. The header has a type, scope and subject:
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
The header is mandatory and the scope of the header is optional.
If the commit reverts a previous commit, it should begin with revert:
, followed by the header of the reverted commit. In the body it should say: This reverts commit <hash>.
, where the hash is the SHA of the commit being reverted.
If the prefix is feat
, fix
or perf
, it will appear in the changelog. However if there is any BREAKING CHANGE, the commit will always appear in the changelog.
Other prefixes are up to your discretion. Suggested prefixes are build
, ci
, docs
,style
, refactor
, and test
for non-changelog related tasks.
Details regarding these types can be found in the official Angular Contributing Guidelines.
The scope could be anything specifying place of the commit change. For example $location
,
$browser
, $compile
, $rootScope
, ngHref
, ngClick
, ngView
, etc...
The subject contains succinct description of the change:
Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes.
Breaking Changes should start with the word BREAKING CHANGE:
with a space or two newlines. The rest of the commit message is then used for this.
A detailed explanation can be found in this document.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
1 existing vulnerabilities detected
Details
Reason
Found 2/25 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
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
Score
Last Scanned on 2025-07-07
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