{"action":"created","issue":{"url":"https://api.github.com/repos/jquery/jquery/issues/2915","repository_url":"https://api.github.com/repos/jquery/jquery","labels_url":"https://api.github.com/repos/jquery/jquery/issues/2915/labels{/name}","comments_url":"https://api.github.com/repos/jquery/jquery/issues/2915/comments","events_url":"https://api.github.com/repos/jquery/jquery/issues/2915/events","html_url":"https://github.com/jquery/jquery/issues/2915","id":132674206,"number":2915,"title":"The husky lint git hook is vulnerable to PATH changes","user":{"login":"mgol","id":1758366,"avatar_url":"https://avatars.githubusercontent.com/u/1758366?v=3","gravatar_id":"","url":"https://api.github.com/users/mgol","html_url":"https://github.com/mgol","followers_url":"https://api.github.com/users/mgol/followers","following_url":"https://api.github.com/users/mgol/following{/other_user}","gists_url":"https://api.github.com/users/mgol/gists{/gist_id}","starred_url":"https://api.github.com/users/mgol/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mgol/subscriptions","organizations_url":"https://api.github.com/users/mgol/orgs","repos_url":"https://api.github.com/users/mgol/repos","events_url":"https://api.github.com/users/mgol/events{/privacy}","received_events_url":"https://api.github.com/users/mgol/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jquery/jquery/labels/Needs%20review","name":"Needs review","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":20,"created_at":"2016-02-10T11:31:58Z","updated_at":"2016-02-17T10:26:32Z","closed_at":null,"body":"The linter git hook added in d94c4539796d02dd0f54e9a3417b660195b844b0 has a significant fault; it creates a pre-commit file where PATH is hard-coded to the one at the end of initial `npm install` (subsequent `npm install`s don't update it). This poses a problem for tools like [nvm](https://github.com/creationix/nvm) where after removing an older Node version (e.g. when a new patch release comes out you might want to remove the older one to not keep vulnerable & outdated releases on the disk) the previous PATH stops being valid, the hook stops working and packages need to be re-installed."},"comment":{"url":"https://api.github.com/repos/jquery/jquery/issues/comments/185140624","html_url":"https://github.com/jquery/jquery/issues/2915#issuecomment-185140624","issue_url":"https://api.github.com/repos/jquery/jquery/issues/2915","id":185140624,"user":{"login":"mgol","id":1758366,"avatar_url":"https://avatars.githubusercontent.com/u/1758366?v=3","gravatar_id":"","url":"https://api.github.com/users/mgol","html_url":"https://github.com/mgol","followers_url":"https://api.github.com/users/mgol/followers","following_url":"https://api.github.com/users/mgol/following{/other_user}","gists_url":"https://api.github.com/users/mgol/gists{/gist_id}","starred_url":"https://api.github.com/users/mgol/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mgol/subscriptions","organizations_url":"https://api.github.com/users/mgol/orgs","repos_url":"https://api.github.com/users/mgol/repos","events_url":"https://api.github.com/users/mgol/events{/privacy}","received_events_url":"https://api.github.com/users/mgol/received_events","type":"User","site_admin":false},"created_at":"2016-02-17T10:26:31Z","updated_at":"2016-02-17T10:26:31Z","body":"@typicode Great, thanks! :) I guess we can treat this ticket as a reminder to update husky in our `package.json` then.\r\n\r\n@jzaefferer What do you think about supporting `nvm` in the same way in commitplease? I know this is applying a workaround for one app only but considering its popularity for managing Node installations..."}}