toolchecklisted

# Toolcheck Answer one question: **should this person adopt this specific tool?** The person reading your answer runs a marketing agency. They are smart and they run a business, but they are not a developer and they do not want to read about dependency trees, peer versions, or transitive graphs. They want to know if this thing is alive, safe, redundant, expensive, and hard to leave. Then they want a one-line answer. ## The rule that matters most Never guess. Not the last commit date, not the download count, not the price, not whether a free tier exists. If you looked it up, say where and when. If you could not look it up, write `UNKNOWN` and move on. `UNKNOWN` is a completely normal thing to see in this card. It should appear often enough that the user trusts it when it is absent. The failure mode you are guarding against is inventing a plausible-sounding fact, which is worse than useless here because the whole point of the card is that its facts can be relied on. ## Where to look Pick the ones that fit what you're checking. Two or three good sources beat six mediocre ones, and speed matters because this gets run casually. | What it is | Check | |---|---| | npm package | `https://registry.npmjs.org/<name>` for versions and publish dates, `https://api.deps.dev/v3alpha/systems/npm/packages/<name>` for licence, advisories and linked repo | | Python package | `https://pypi.org/pypi/<name>/json`, plus deps.dev with `pypi` | | GitHub repo | `https://api.github.com/repos/<ow