Gathering detailed insights and metrics for @marionebl/conventional-commits-parser
Gathering detailed insights and metrics for @marionebl/conventional-commits-parser
deprecated, instead use https://github.com/conventional-changelog/conventional-changelog monorepo
Installations
npm install @marionebl/conventional-commits-parserDeveloper Guide
BETA
Typescript
No
Module System
N/A
Node Version
8.5.0
NPM Version
2.15.11
Score
65.5
Supply Chain
97.9
Quality
72.1
Maintenance
50
Vulnerability
98.9
License
Releases
29
Languages
1
JavaScript
JavaScript (100%)
Developer
conventional-changelog
Download Statistics
Total Downloads
323,700
Last Day
109
Last Week
260
Last Month
1,245
Last Year
12,804
GitHub Statistics
14 Stars
157 Commits
8 Forks
2 Watchers
1 Branches
6 Contributors
Updated on Jan 02, 2025
Maintainers
1
Package Meta Information
Latest Version
3.0.0
Package Id
@marionebl/conventional-commits-parser@3.0.0
Size
10.85 kB
NPM Version
2.15.11
Node Version
8.5.0
Published on
Nov 01, 2017
Total Downloads
Cumulative downloads
Total Downloads
323,700
Last Day
626.7%
109
Compared to previous day
Last Week
-1.5%
260
Compared to previous week
Last Month
-13.2%
1,245
Compared to previous month
Last Year
24.2%
12,804
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Parse raw conventional commits
Conventional Commit Message Format
A minimum input should contain a raw message.
Each commit message consists of a merge header, a header (mandatory), a body and a footer. Mention (optional) someone using the @ notation.
<merge>
<header>
<body>
<footer>
merge
The merge header may optionally have a special format that includes other parts, such as branch, issueId or source.
Merge branch <branch>
Merge pull request <issue-id> from <source>
header
The header may optionally have a special format that includes other parts, such as type, scope and subject. You could reference (optional) issues here.
<type>(<scope>): <subject>
footer
The footer should contain any information about Important Notes (optional) and is also the place to reference (optional) issues.
<important note>
<references>
other parts
This module will only parse the message body. However, it is possible to include other fields such as hash, committer or date.
My commit message
-sideNotes-
It should warn the correct unfound file names.
Also it should continue if one file cannot be found.
Tests are added for these
Then sideNotes will be It should warn the correct unfound file names.\nAlso it should continue if one file cannot be found.\nTests are added for these. You can customize the fieldPattern.
Install
1$ npm install --save conventional-commits-parser
Usage
1var conventionalCommitsParser = require('conventional-commits-parser'); 2 3conventionalCommitsParser(options);
It returns a transform stream and expects an upstream that looks something like this:
'feat(scope): broadcast $destroy event on scope destruction\nCloses #1'
'feat(ng-list): Allow custom separator\nbla bla bla\n\nBREAKING CHANGE: some breaking change.\nThanks @stevemao\n'
Each chunk should be a commit. The downstream will look something like this:
1{ type: 'feat', 2 scope: 'scope', 3 subject: 'broadcast $destroy event on scope destruction', 4 merge: null, 5 header: 'feat(scope): broadcast $destroy event on scope destruction', 6 body: null, 7 footer: 'Closes #1', 8 notes: [], 9 references: 10 [ { action: 'Closes', 11 owner: null, 12 repository: null, 13 issue: '1', 14 raw: '#1', 15 prefix: '#' } ], 16 mentions: [], 17 revert: null } 18{ type: 'feat', 19 scope: 'ng-list', 20 subject: 'Allow custom separator', 21 merge: null, 22 header: 'feat(ng-list): Allow custom separator', 23 body: 'bla bla bla', 24 footer: 'BREAKING CHANGE: some breaking change.\nThanks @stevemao', 25 notes: 26 [ { title: 'BREAKING CHANGE', 27 text: 'some breaking change.\nThanks @stevemao' } ], 28 references: [], 29 mentions: [ 'stevemao' ], 30 revert: null }
API
conventionalCommitsParser([options])
Returns an transform stream. If there is any malformed commits it will be gracefully ignored (an empty data will be emitted so down stream can notice).
options
Type: object
mergePattern
Type: regex or string Default: null
Pattern to match merge headers. EG: branch merge, GitHub or GitLab like pull requests headers. When a merge header is parsed, the next line is used for conventionnal header parsing.
For example, if we have a commit
Merge pull request #1 from user/feature/feature-name
feat(scope): broadcast $destroy event on scope destruction
We can parse it with these options and the default headerPattern:
1{ 2 mergePattern: /^Merge pull request #(\d+) from (.*)$/, 3 mergeCorrespondence: ['id', 'source'] 4}
mergeCorrespondence
Type: array of string or string Default: null
Used to define what capturing group of mergePattern.
If it's a string it will be converted to an array separated by a comma.
headerPattern
Type: regex or string Default: /^(\w*)(?:\(([\w\$\.\-\* ]*)\))?\: (.*)$/
Used to match header pattern.
headerCorrespondence
Type: array of string or string Default ['type', 'scope', 'subject']
Used to define what capturing group of headerPattern captures what header part. The order of the array should correspond to the order of headerPattern's capturing group. If the part is not captured it is null. If it's a string it will be converted to an array separated by a comma.
referenceActions
Type: array of string or string Default:
[ 'close', 'closes', 'closed', 'fix', 'fixes', 'fixed', 'resolve', 'resolves', 'resolved' ]
Keywords to reference an issue. This value is case insensitive. If it's a string it will be converted to an array separated by a comma.
Set it to null to reference an issue without any action.
issuePrefixes
Type: array of string or string Default: ['#']
The prefixes of an issue. EG: In gh-123 gh- is the prefix.
noteKeywords
Type: array of string or string Default: ['BREAKING CHANGE']
Keywords for important notes. This value is case insensitive. If it's a string it will be converted to an array separated by a comma.
fieldPattern
Type: regex or string Default: /^-(.*?)-$/
Pattern to match other fields.
revertPattern
Type: regex or string Default: /^Revert\s"([\s\S]*)"\s*This reverts commit (\w*)\./
Pattern to match what this commit reverts.
revertCorrespondence
Type: array of string or string Default: ['header', 'hash']
Used to define what capturing group of revertPattern captures what reverted commit fields. The order of the array should correspond to the order of revertPattern's capturing group.
For example, if we had commit
Revert "throw an error if a callback is passed"
This reverts commit 9bb4d6c.
If configured correctly, the parsed result would be
1{ 2 revert: { 3 header: 'throw an error if a callback is passed', 4 hash: '9bb4d6c' 5 } 6}
It implies that this commit reverts a commit with header 'throw an error if a callback is passed' and hash '9bb4d6c'.
If it's a string it will be converted to an array separated by a comma.
warn
Type: function or boolean Default: function() {}
What warn function to use. For example, console.warn.bind(console) or grunt.log.writeln. By default, it's a noop. If it is true, it will error if commit cannot be parsed (strict).
conventionalCommitsParser.sync(commit, [options])
The sync version. Useful when parsing a single commit. Returns the result.
commit
A single commit to be parsed.
options
Same as the options of conventionalCommitsParser.
CLI
You can use cli to practice writing commit messages or parse messages from files. Note: the sample output might be different. It's just for demonstration purposes.
1$ npm install --global conventional-commits-parser
If you run conventional-commits-parser without any arguments
1$ conventional-commits-parser
You will enter an interactive shell. To show your parsed output enter "return" three times (or enter your specified separator).
1> fix(title): a title is fixed 2 3 4{"type":"fix","scope":"title","subject":"a title is fixed","header":"fix(title): a title is fixed","body":null,"footer":null,"notes":[],"references":[],"revert":null}
You can also use cli to parse messages from files.
If you have log.txt
1feat(ngMessages): provide support for dynamic message resolution 2 3Prior to this fix it was impossible to apply a binding to a the ngMessage directive to represent the name of the error. 4 5BREAKING CHANGE: The `ngMessagesInclude` attribute is now its own directive and that must be placed as a **child** element within the element with the ngMessages directive. 6 7Closes #10036 8Closes #9338
And you run
1$ conventional-commits-parser log.txt 2# or 3$ cat log.txt | conventional-commits-parser
An array of json will be printed to stdout.
1[ 2{"type":"feat","scope":"ngMessages","subject":"provide support for dynamic message resolution","header":"feat(ngMessages): provide support for dynamic message resolution","body":"Prior to this fix it was impossible to apply a binding to a the ngMessage directive to represent the name of the error.","footer":"BREAKING CHANGE: The `ngMessagesInclude` attribute is now its own directive and that must be placed as a **child** element within the element with the ngMessages directive.\nCloses #10036\nCloses #9338","notes":[{"title":"BREAKING CHANGE","text":"The `ngMessagesInclude` attribute is now its own directive and that must be placed as a **child** element within the element with the ngMessages directive."}],"references":[{"action":"Closes","owner":null,"repository":null,"issue":"10036","raw":"#10036"},{"action":"Closes","owner":null,"repository":null,"issue":"9338","raw":"#9338"}],"revert":null} 3]
Commits should be split by at least three newlines (\n\n\n) or you can specify a separator as the second argument.
Eg: in log2.txt
1 2docs(ngMessageExp): split ngMessage docs up to show its alias more clearly 3=== 4 5fix($animate): applyStyles from options on leave 6 7Closes #10068
And you run
1$ conventional-commits-parser log2.txt '==='
1[ 2{"type":"docs","scope":"ngMessageExp","subject":"split ngMessage docs up to show its alias more clearly","header":"docs(ngMessageExp): split ngMessage docs up to show its alias more clearly","body":null,"footer":null,"notes":[],"references":[],"revert":null} 3, 4{"type":"fix","scope":"$animate","subject":"applyStyles from options on leave","header":"fix($animate): applyStyles from options on leave","body":null,"footer":"Closes #10068","notes":[],"references":[{"action":"Closes","owner":null,"repository":null,"issue":"10068","raw":"#10068"}],"revert":null} 5]
Will be printed out.
You can specify one or more files. The output array will be in order of the input file paths. If you specify more than one separator, the last one will be used.
License
MIT © Steve Mao
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
Found 2/30 approved changesets -- score normalized to 0
Reason
project is archived
Details
- Warn: Repository is archived.
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
license file not detected
Details
- Warn: project does not have a license file
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 3 are checked with a SAST tool
Score
2.6
/10
Last Scanned on 2025-05-05
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