-
Notifications
You must be signed in to change notification settings - Fork 55
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
Combine efforts with HTTPArchive/wappalyzer #189
Comments
Our goal is to keep the technologies in sync & increasing them, while maintaining legacy implementations by keeping the old wappalyzer structure; we want to keep this repo as is, with just the detectors and soon we will start releasing language based implementations for the community to use if they want... I know httparchive reputation and i know they will keep it up, but their solution for maintenance is not what we have in mind(https://docs.google.com/document/d/1jGhvtpaatOJTh5LGcd42hyrt8lNRmK_f4PaCHf3kR_M/edit#heading=h.4qcqv7qpi4of), we want to review PR, validate all detectors with proper CI/CD, and we are working in many bots for technology discovery so we can automate as much as we can as well as programming language implementations, while having at least one person fully dedicated to it. We truly believe that this kind of solution will work if its open source, more people will be using it, testing, reporting and contributing. We are willing to negotiate with anyone who's trying is to help the community and try to make it as stable as possible for future-proof, we understand it's very difficult to trust a new fork owner, the quality might decrease and a strict organization is required. |
@enthec-opensource Did you already had some discussions with HTTPArchive maintainers ? I would be surprised that they don't want to go on Also, you said:
Are you speaking about a full-time employee ? I don't see any contributions in the last two months. |
After lots of looking, the two most active forks are this one and https://github.com/HTTPArchive/wappalyzer. I was wondering if it made sense to join forces in a single repo.
The text was updated successfully, but these errors were encountered: