Remove deprecation notice

[ghost]

#209 related.

Need to figure out what's needed to remove the deprecation notice. I've updated the repo title to [CURRENTLY DEPRECATED] to hint at revival. Will dig into this at some point unless some in the org (current or future) gets to it first.

[gtramontina]

To "un-deprecate" it with npm, it is just a matter of setting the deprecation message to an empty string, as per the docs https://docs.npmjs.com/cli/deprecate

To un-deprecate a package, specify an empty string ("") for the message argument.

[ghost]

@gtramontina thanks. I will look into taking care of this with a new minor as soon as I'm able to get off my current network, which is blocking my 22 and preventing PGP.

[gtramontina]

Done! 👍 A patch release went out with #218.

[G-Rath]

@gtramontina given that the poster has deleted their github account, and ghooks hasn't seen a new version or activity (aside from dependabot) in a few years, might be time to re-deprecate the package to reduce confusion?

(I stumbled upon an old project using this and had to hunt around a bit to confirm that it's been abandoned).