Gathering detailed insights and metrics for @mixmaxhq/semantic-commitlint
Gathering detailed insights and metrics for @mixmaxhq/semantic-commitlint
Gathering detailed insights and metrics for @mixmaxhq/semantic-commitlint
Gathering detailed insights and metrics for @mixmaxhq/semantic-commitlint
📦🚀 + 📓 A continuous integration build tool to ensure all new commits meet your commit message format! ️️
npm install @mixmaxhq/semantic-commitlint
Typescript
Module System
Node Version
NPM Version
48.5
Supply Chain
66.6
Quality
78.7
Maintenance
50
Vulnerability
96.7
License
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
1 Stars
42 Commits
1 Watchers
4 Branches
Updated on Oct 29, 2020
Latest Version
1.0.3
Package Id
@mixmaxhq/semantic-commitlint@1.0.3
Unpacked Size
9.19 kB
Size
3.83 kB
File Count
5
NPM Version
6.13.0
Node Version
10.16.0
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
5
📦🚀 + 📓 A continuous integration build tool to ensure all new commits meet your commit message format!
semantic-release
that asks commitlint
to lint new commit messages that
have not been included in a previous releasesemantic-release
and
commitlint
for an easy install1npm install semantic-commitlint --save-dev
Add the following to your semantic-release
release block (e.g. in the release
field of your
package.json
)
1{ 2 "verifyRelease": ["semantic-commitlint"] 3}
Setup semantic-release authentication for CI
semantic-commitlint
currently only supports @commitlint/config-conventional
- please open a PR
if you need support for other configurations!
Simply run semantic-release
as normal as part of your CI build process
If there are unreleased commits that shouldn't fail a build, then add them to the
SEMANTIC_COMMITLINT_SKIP
environment variable as comma-separated GIT SHAs. This should be
uncommon, provided your development workflow lints the commits before they get added to the release
branch.
1// This is the package.json of the package you're trying to publish. 2// Just add the SEMANTIC_COMMITLINT_SKIP prefix to the semantic-release command! 3{ 4 "scripts": { 5 "semantic-release": "SEMANTIC_COMMITLINT_SKIP=a1be371 semantic-release" 6 } 7}
This project just ties together some functionality from two external projects. For all other config options make sure to read through the docs.
Not all features implemented in semantic-release
and commitlint
are currently available when
using semantic-commtlint
. If you have a suggestion, please
open an issue. Thanks!
semantic-commitlint is licensed under the MIT Open Source license. For more information, see the LICENSE file in this repository.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 4/23 approved changesets -- score normalized to 1
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
80 existing vulnerabilities detected
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