Gathering detailed insights and metrics for core-validate-commit
Gathering detailed insights and metrics for core-validate-commit
Installations
npm install core-validate-commitDeveloper Guide
BETA
Typescript
No
Module System
ESM
Node Version
20.14.0
NPM Version
10.7.0
Releases
Unable to fetch releases
Languages
1
JavaScript
JavaScript (100%)
Developer
nodejs
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
54 Stars
175 Commits
52 Forks
9 Watchers
8 Branches
43 Contributors
Updated on Jun 19, 2025
Maintainers
7
Package Meta Information
Latest Version
4.1.0
Package Id
core-validate-commit@4.1.0
Unpacked Size
32.79 kB
Size
9.73 kB
File Count
22
NPM Version
10.7.0
Node Version
20.14.0
Published on
Aug 05, 2024
Total Downloads
Cumulative downloads
Total Downloads
NaN
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
Weekly Downloads
Monthly Downloads
Yearly Downloads
core-validate-commit
Validate the commit message for a particular commit in node core
Install
1$ npm install [-g] core-validate-commit
Usage
1# for a single commit 2$ core-validate-commit <sha> 3 4# validate since <sha> 5$ git rev-list <sha>..HEAD | xargs core-validate-commit 6 7# list all rules 8$ core-validate-commit --list 9 fixes-url enforce format of Fixes URLs 10 line-after-title enforce a blank newline after the commit title 11 line-length enforce max length of lines in commit body 12 metadata-end enforce that metadata is at the end of commit messages 13 pr-url enforce PR-URL 14 reviewers enforce having reviewers 15 subsystem enforce subsystem validity 16 title-format enforce commit title format 17 title-length enforce max length of commit title
To see a list of valid subsystems:
1$ core-validate-commit --list-subsystem
Valid subsystems are also defined in lib/rules/subsystem.js.
Test
1$ npm test
Author
Evan Lucas
License
MIT (See LICENSE for more info)
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/nodejs/.github/SECURITY.md:1
- Info: Found linked content: github.com/nodejs/.github/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: github.com/nodejs/.github/SECURITY.md:1
- Info: Found text in security policy: github.com/nodejs/.github/SECURITY.md:1
Reason
Found 15/30 approved changesets -- score normalized to 5
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/node.js.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/nodejs/core-validate-commit/node.js.yml/main?enable=pin
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/node.js.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 22 are checked with a SAST tool
Score
4.5
/10
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