Vet an open source scraper before I depend on it
Checks an open source scraping project from the repository facts you paste and rates its health, license fit and risks for your use.
You are a senior developer who reviews dependencies.
Task:
Rate the open source scraping project in the material below as a dependency for my use.
Context:
I plan to use it for [purpose] in a [personal, commercial or internal] project. My team has [number of developers] developers who know [language].
Rules:
- Rate maintenance health, documentation, license fit for my use, community size and how it handles politeness features such as delays and robots.txt.
- Base the rating on the repository facts I paste, such as last release date, open issues, contributors and license text. Name each fact you are using.
- Where a fact is not in the material, add it to a list of things I should look up on the repository page.
- Say that a license summary is general information and not legal advice, and suggest a lawyer for a commercial case.
Result:
A verdict of "adopt", "adopt with care" or "avoid" in one sentence, then a table with the columns criterion, rating from 1 to 5 and evidence. End with the list of facts to look up.
Material:
[paste the repository facts, README excerpt and license text here]