Dirk Stolle

> [...] it's likely easier for me to help you land this and release a new version than it is to remove this dependency from our code. Yes, that would...

@BurntSushi: Just a friendly reminder that is has been over a year since the PR was created. If there is anything wrong with the changes in this PR and this...

Hmm. It probably wouldn't have hurt to add those changes before adding the warning in commit 62b0e31f277e34e89fb7060f6bae5be16f05d00c. :disappointed: The entries for some of the newer releases are already here, so...

> @striezel tests are failing on master in node < 4, and altho i reviewed this PR, i don't typically maintain browserify, so it needs to wait for the maintainers....

> So this will not get fixed? It doesn't look like it will get fixed. As things are now, this package has basicially been unmaintained for almost three years. :(...

@bluss: I just force pushed some changes, because meanwhile v4 of [`actions/checkout`](https://github.com/actions/checkout) has been released, so the PR should use that newer version.

@anjin cc @nickmerwin > We'll take a look, thanks for the PR! Can you give us a status update on this on? How are things progressing?

Looks like a duplicate of #876. Maybe one of those pull requests can be closed.

@PixelMedia1: The file that is added in this pull requests looks like a placeholder and not like a real `SECURITY.md` file. A real file should actually tell about a project's...

@shama: I am aware that the AppVeyor build checks still fail, but they are failing for the current master commit (fc8458ee34), too. See https://ci.appveyor.com/project/gruntjs/grunt-contrib-watch/builds/38343248. However, Travis CI is fine again,...