Security News
The Risks of Misguided Research in Supply Chain Security
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
jira-precommit-hook
Advanced tools
Git commit hook to verify commit messages are tagged with a JIRA issue number
Goals:
Currently only configured for read-only access to JIRA.
In order to communicate with your JIRA server, a .jirarc file needs to be placed in the root of the repo.
{
"projectName": "<Name of JIRA project - REQUIRED>",
"host":"<URL location of JIRA project - REQUIRED>",
"protocol":"[default:http|https]",
"port": default:80,
"version": default:2,
"verbose": default:false,
"strictSSL": default:true
}
To install, run the following with npm:
> npm install jira-precommit-hook
If the hooks directory in your .git folder is symlinked, the module will be unable to find it. To avoid this, do not symlink your hooks folder inside of your project's git directory.
In order to make a successful commit with the precommit hook, ALL issues being committed must meet the following requirements:
At least one issue being committed must meet the following requirements:
By default you will get a joke presented to you upon a successful commit. This is two-fold, first to get you accustomed to the commit hook so you are aware when it's not present. The second is for some comic relief at work, cause we all need it.
> ./node_modules/.bin/jira-precommit jokes disable
> ./node_modules/.bin/jira-precommit jokes enable
To disable To disable the joke feature simply delete the .chuckNorris file from your home directory.
FAQs
Git commit hook to verify commit messages are tagged with a JIRA issue number
We found that jira-precommit-hook demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.