Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What up with the declandewet/common-tags repo? #214

Closed
dancoates opened this issue Nov 8, 2021 · 5 comments
Closed

What up with the declandewet/common-tags repo? #214

dancoates opened this issue Nov 8, 2021 · 5 comments

Comments

@dancoates
Copy link

This repo (https://github.com/declandewet/common-tags) is linked in the package.json and appears on the npm package page

https://www.npmjs.com/package/common-tags

it appears that it was recently taken over by this person: https://hackerone.com/codermak?type=user

Is access to that repo tied at all to the ability to alter the code of this repo or to publish the common-tags package?

@fatfisz
Copy link
Collaborator

fatfisz commented Nov 8, 2021

That's a shame; I can only assure you that the repo is still in the right hands.

It looks like the lib's creator Declan de Wet has changed his GitHub handle to zspecza and the declandewet handle was indeed taken over by some random person. The unfortunate result is that while previously GitHub redirected from
https://github.com/declandewet/common-tags to https://github.com/zspecza/common-tags, this doesn't happen anymore.

I'm struggling to find time to follow up with this project's roadmap, but I'll at least take care of the problem, since it's very misleading. I'll be releasing a new version with the updated repo link soon ™️ (I don't have internet at my new home yet, this should be resolved in a matter of days).

In the meantime I'm pinning this issue for posterity. I won't be contacting the person who took over the declandewet handle, because I don't think it's going to be productive.

@fatfisz fatfisz pinned this issue Nov 8, 2021
@dancoates
Copy link
Author

Thanks @fatfisz that makes sense, and it is reassuring that there isn't any risk to this project.

@fatfisz
Copy link
Collaborator

fatfisz commented Nov 11, 2021

I just published a new version to npm, at least that's what npm info is telling me:
image

The version on the npm page is still 1.8.0, probably because of caching. I'll close the issue once I see new links working there.

@fatfisz
Copy link
Collaborator

fatfisz commented Nov 11, 2021

... and it works!
image

@fatfisz fatfisz closed this as completed Nov 11, 2021
@dancoates
Copy link
Author

brilliant, thanks @fatfisz for the quick update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants