the security placeholder package should fix that issue, shouldn't it? i was pretty shocked that they didn't do that in the initial instance - tell whoever owned

the security placeholder package should fix that issue, shouldn't it? i was pretty shocked that they didn't do that in the initial instance - tell whoever owned 'kik' that they had to remove it due to a trademark claim, but then blocked the name and told kik-the-company that it wasn't available to be used as an npm package name.