Gathering detailed insights and metrics for @dgc-org/commitlint-config-conventional-changelog-for-jira
Gathering detailed insights and metrics for @dgc-org/commitlint-config-conventional-changelog-for-jira
Gathering detailed insights and metrics for @dgc-org/commitlint-config-conventional-changelog-for-jira
Gathering detailed insights and metrics for @dgc-org/commitlint-config-conventional-changelog-for-jira
npm install @dgc-org/commitlint-config-conventional-changelog-for-jira
Typescript
Module System
Node Version
NPM Version
68.9
Supply Chain
99.2
Quality
82.3
Maintenance
100
Vulnerability
100
License
JavaScript (89.06%)
Shell (10.94%)
Love this project? Help keep it running — sponsor us today! 🚀
Total Downloads
52,735
Last Day
69
Last Week
336
Last Month
1,244
Last Year
17,990
MIT License
1 Stars
22 Commits
6 Watchers
5 Branches
1 Contributors
Updated on Jul 22, 2022
Latest Version
1.2.6
Package Id
@dgc-org/commitlint-config-conventional-changelog-for-jira@1.2.6
Unpacked Size
9.97 kB
Size
3.70 kB
File Count
5
NPM Version
6.14.15
Node Version
14.18.1
Cumulative downloads
Total Downloads
Last Day
-1.4%
69
Compared to previous day
Last Week
-1.2%
336
Compared to previous week
Last Month
33%
1,244
Compared to previous month
Last Year
-22.3%
17,990
Compared to previous year
1
Shareable commitlint
config enforcing the Angular commit convention and Jira Smart Commit Syntax. Based on @commitlint/config-angular.
Use with @dgc-org/cz-conventional-changelog-for-jira, @commitlint/cli.
1npm install --save-dev @dgc-org/commitlint-config-conventional-changelog-for-jira @commitlint/cli 2echo "module.exports = {extends: ['@dgc-org/commitlint-config-conventional-changelog-for-jira']};" > commitlint.config.js
In some cases it might be useful to be able to skip linting, e.g. when lacking access to Jira or having to do nasty things in GitOps. This configuration skips the linting process altogether if either of these conditions are satisfied:
WIP:
, e.g. WIP: the office is burning down, need to save my work
COMMITLINT_DISABLE
is set to true
(case-insensitive) or 1
This mechanism should only be used in situations where there's no alternative to it, rather than to ignore fixable validation failures.
The following rules are considered problems for @dgc-org/commitlint-config-conventional-changelog-for-jira
and will yield a non-zero exit code when not met.
Consult docs/rules for a list of available rules.
type
is found in valuealways
1[ 2 "feat", 3 "fix", 4 "docs", 5 "refactor", 6 "test", 7 "style", 8 "build", 9 "ci", 10 "chore", 11 "revert", 12 "perf", 13 "wip", 14]
1echo "foo: some message" # fails 2echo "fix: some message" # passes
type
is in case value
always
1'lowerCase'
1echo "FIX: some message" # fails 2echo "fix: some message" # passes
type
is emptynever
1echo ": some message" # fails 2echo "fix: some message" # passes
scope
is in case value
always
1'lowerCase'
1echo "fix(SCOPE): some message" # fails 2echo "fix(scope): some message" # passes
subject
is in one of the cases ['sentence-case', 'start-case', 'pascal-case', 'upper-case']
never
1echo "fix(SCOPE): Some message" # fails 2echo "fix(SCOPE): Some Message" # fails 3echo "fix(SCOPE): SomeMessage" # fails 4echo "fix(SCOPE): SOMEMESSAGE" # fails 5echo "fix(scope): some message" # passes 6echo "fix(scope): some Message" # passes
subject
is emptynever
1echo "fix:" # fails 2echo "fix: some message" # passes
subject
ends with value
never
1'.'
1echo "fix: some message." # fails 2echo "fix: some message" # passes
header
has value
or less charactersalways
172
1echo "fix: some message that is way too long and breaks the line max-length by several characters" # fails 2echo "fix: some message" # passes
The following rules are considered warnings for @dgc-org/commitlint-config-conventional-changelog-for-jira
and will print warning messages when not met.
always
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
Found 0/22 approved changesets -- score normalized to 0
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
branch protection not enabled on development/release branches
Details
Reason
12 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-02-17
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