-
Notifications
You must be signed in to change notification settings - Fork 13
Explanation of fork in README #179
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
Comments
I agree... there have been a lot of supply chain attacks and I've been the target of many phishing attempts, hence why I hid my personal details from my GitHub page (I assume that a web scraper is collecting emails targeting maintainers of projects with more than a hundred or so stars). Ever since I hid my email, the emails have stopped for the most part. |
Gentle ping on this :) |
Sorry about that. My schedule for contributing has been out of sorts. I was appointed by Dana to have Push permissions to This project is a pure Python distribution in wheels, so there isn't any malicious code hidden in compiled wheels because they aren't compiled to begin with and I also use trusted publishing to PyPi to demonstrate that these files came directly from GitHub. I'll add this note to the readme. |
It would be nice to have a proper description of why this fork exists in README so stakeholders and reviewers can better understand why their code switches dependency to kafka-python-ng.
This makes code reviews of the switch easier, and also helps with the worries some have due to the increase in supply chain attacks in recent years.
The text was updated successfully, but these errors were encountered: