
Security News
Node.js Drops Bug Bounty Rewards After Funding Dries Up
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.
@dwmt/commitlint-plugin-github-type
Advanced tools
Check if your commit messages start with a GitHub issue reference and a type.
Commitlint plugin to check if your commit messages start with an issue number and a type.
Accepts commit messages like:
#1/feat: implemented a new message handler
#729/fix: removed erroneous handling of a key
If you want to lint your commits with github-type, follow along:
npm i @commitlint/cli husky @dwmt/commitlint-plugin-github-type @dwmt/commitlint-config-github-type -D
// commitlint.config.js
module.exports = {
plugins: ['@dwmt/commitlint-plugin-github-type'],
extends: ['@dwmt/commitlint-config-github-type'],
}
commit-msg hook
mkdir .husky
npx husky add .husky/commit-msg "npx --no-install commitlint --edit $1"
You can find detailed instructions regarding the local setup of Commitlint and Husky at Commitlint Local Setup.
Please see the README of the parent monorepo.
FAQs
Check if your commit messages start with a GitHub issue reference and a type.
We found that @dwmt/commitlint-plugin-github-type demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.

Security News
The Axios compromise shows how time-dependent dependency resolution makes exposure harder to detect and contain.

Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.