![Namecheap Takes Down Polyfill.io Service Following Supply Chain Attack](https://cdn.sanity.io/images/cgdhsj6q/production/6af25114feaaac7179b18127c83327568ff592d1-1024x1024.webp?w=800&fit=max&auto=format)
Security News
Namecheap Takes Down Polyfill.io Service Following Supply Chain Attack
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
@superkoders/commitlint-config
Advanced tools
Readme
Our custom commitlint rules.
npm i -D @superkoders/commitlint-config
This tells commitlint when to locate our rules. You can also override the rules here, if you have some exception on a given project.
module.exports = {
extends: ["@superkoders/commitlint-config"],
};
npm i -D husky
Add to the package.json
{
"husky": {
"hooks": {
"commit-msg": "commitlint -E HUSKY_GIT_PARAMS"
}
},
}
When commiting, we stick with conventional config settings. Permitted keywords are those:
feat: add or extend backwards compatible functionality. It bumps version by minor and reset patch number to 0.
fix: bugfixes, it bumps version by patch.
refactor: code changes, which don't fix anything nor adds new functionality
perf: performance related changes
tpl: update templates
revert: for reverting commits
ui: UI adjustments
style: code changes, which don't alter its function (eg. formatting)
content: Images, text edits and alike
docs: only documentation changes
test: add or edit tests
build: changes related to project build (eg. webpack)
ci: changes related to project integration (eg. CI)
config: Config and rules changes
chore: other changes, which don't alter source or test code (eg. release new version)
when introducing backwards incompatible API changes (which bumps version by MAJOR), indicate it with keyword BREAKING CHANGE
written at the very beginning of commit body, ideally with additional information. Commit subject should be as usual - ketyword and explanation. Eg.
refactor: unify componentA and componentB, change input data
BREAKING CHANGE here can be another explanation and reasoning
For more on commitlint visit official documentation.
FAQs
SUPERKODERS commitlint configuration
We found that @superkoders/commitlint-config demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.
Security News
A JavaScript library maintainer is under fire after merging a controversial PR to support legacy versions of Node.js.