Find a tool

Open Find a tool. Say what you want to build, like “web scraper for Amazon prices”, and press “Search”, or press one of the examples.

• “For your project” names the project the results are fitted to, and its language. Only your words and the project's language are sent, never its name, its files or its code.

Up to eight tools, best first. Each says what it does, its stars, when it was last updated, its license in plain words (like “OK in a paid product”) and its language. A label says why: “Best for you”, “Simpler”, or “Avoid” (for example archived, or not kept up). When your search names a website, “Check first” says what that site allows.

Press a tool to open it: why it fits, what it needs, its license in full (plain words, not legal advice), and its trust checks, each a dot with words. “Open on GitHub” opens its page.

• “Don't use” marks a tool that failed the trust checks: stars that came too fast from brand-new accounts, a name that copies a well-known tool, or a README that asks you to download and run something. It has no Use this, for anyone.
• An “Avoid” tool has “Use anyway…” in place of Use this: it says again why it's marked Avoid, and only Approve goes on.
• A tool Nirvaana hasn't fully checked yet is marked Avoid until it has.
• Nothing a README says is ever run: its words are read as data only.

By how well it fits what you said, how well kept it is, its license, and your project's language. The trust checks come first: Avoid and Don't use always sit below the rest, whatever their stars. The labels and their one-line reasons are written by Nirvaana from the facts it checked, never from a tool's own words.

Use this sets the tool up in your project. A sheet says what will happen, and nothing starts until you press Approve on the plan's card in Chat.

• It installs only the package and version Nirvaana checked for that tool, with install scripts off and only the project's own npm settings. If anything else would change where packages come from (another package, a changed one, a lock file or a settings file, even one git ignores), nothing is installed and it says why. A Python package installs only ready-built (a wheel); one without a wheel would run its own setup.py, so it asks you a second time. Nothing a README says is ever run.
• It works in Python projects and in JavaScript or TypeScript projects that use npm (not workspaces yet), and needs ship mode on. The work runs on your computer, through the Mac and Windows app.