playrote.play.v1

ssakshamsai26/dependency-whyv0.2.2Public

Dependency why

Dependencies survive long after the feature, plugin, build step, or transitive assumption that introduced them has been forgotten.

Read the full description

Dependency Why performs a bounded local static investigation across package manifests, imports, configuration, scripts, and text references to explain the strongest observable reason a named dependency appears to exist. Its report distinguishes direct application usage, tooling/configuration evidence, manifest-only evidence, and no obvious static usage; dynamic loading, generated code, lockfile-only transitives, and runtime behavior remain explicitly UNKNOWN. It is a removal-review starting point, not a license/security verdict or permission to delete a package. Read-only: it never installs, removes, upgrades, executes, or contacts a package registry.

  • Published 4 Sep 2026
  • Download 1
  • Needs rote 0.62.0+
  • Digest sha256:b87554445d60…
  • Reference sakshamsai26/dependency-why@0.2.2

Before you run it1 local tool

Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.

  • ○
    python3local tool

    Must be on your PATH when used. minimum version undeclared.

Inputs2, all required

rote asks for these before running and shows the defaults it will use.

  • Rootroot

    Absolute repository path you are authorized to inspect.

    requiredstringcustom value allowed
  • Dependencydependency

    Package or dependency name to investigate.

    requiredstringcustom value allowed

What it changes

No write operations are declared in this version's manifest.

Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.

Runtime details
  • rote CLIversion 0.62.0 or newer
  • Servicesnone declared
  • Digestsha256:b87554445d6049deca945e6585e7c0eea0212f489fd996366a4181f1e0df69f3
  • Archive size6660 bytes
  • Published2026-09-04T09:40:03.407772+00:00
  • Published withrote 0.77.0

Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.

A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.