should-i-use

Reviewed Jan 1, 2000.

• tools: 6 tools scanned
• metadata: scanned
• packages: 1 checked

No findings.

Tools (6)

• pick_library

  Given a coding task, recommend 1-3 libraries from the should-i-use index with one-line reasoning and an honest warning about the top pick. Use before installing anything.

• should_i_use

  Honest verdict on a specific library: 4-axis scores with reasons, when to skip it, and maintenance signals (last push, weekly downloads).

• alternatives

  Curated alternatives to a library, each with a one-line "prefer it when" and a verdict if the alternative is also indexed.

• how_do_i

  Return the 1-2 best code snippets for a task with a library, plus the gotcha for each. Snippets are correct for the indexed version. Far cheaper in tokens than a docs dump.

• audit_dependencies

  Audit a project's dependencies for unmaintained packages, unstable APIs, and documented reasons to switch. Pass the contents of package.json, requirements.txt, or pyproject.toml. Returns only the dependencies worth a decision, not a report on every line. Run this before working in an unfamiliar codebase.

• docs_link

  Official docs URL and GitHub repo for a library, one line each. Use when the clamped answers are not enough.