Skip to main content
Glama

Related Servers

Alternatives to unripe

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables checking whether software packages are deprecated, archived, stale, active, or unknown with supporting evidence, auditing dependency manifests, and looking up runtime support and end-of-life dates.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to fetch the real latest versions of packages from npm, PyPI, crates.io and the Go module proxy, then check manifests or whole projects for outdated dependencies and rewrite them in place. It also reports the current releases and underlying dependency stacks of AI coding tools like Claude Code, Codex and Gemini CLI.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to vet an npm release against the package's own history — publisher, provenance, install scripts, new dependencies, code changes — before installing or upgrading it. Returns an ALLOW / REVIEW / BLOCK verdict with supporting evidence, what other checks say, and the safe version to install instead.
      7
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to ground dependency setup, compatibility checks, and major-version migration advice in a project's real runtime, lockfiles, and config files. It parses local project state and npm registry metadata deterministically, then returns tag-pinned install commands, breaking changes, and upgrade steps rather than generic documentation.
      5
      95 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to retrieve the latest stable versions of packages and tools across multiple ecosystems, preventing outdated dependency versions in generated code.
      4
      230 PyPI
      9
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly different object: project configuration/policy, a single package version, and lockfiles across a directory. Their boundaries are easy to infer, and an agent should not confuse checking one package with scanning all lockfiles or reading cooldown settings.

    Naming Consistency4/5

    All names use snake_case, and two follow a clear verb_noun pattern (check_package, check_lockfiles). cooldown_settings is a noun phrase rather than a verb-led name, but it remains readable and semantically clear.

    Tool Count5/5

    Three tools is well scoped for a focused minimum-release-age auditing server. Each tool has a distinct role: inspect settings, inspect one package, and inspect lockfiles.

    Completeness3/5

    The server covers policy inspection and two important audit paths, but there is no remediation or bulk upgrade tool to fix lockfiles or manifests. Agents can likely work around this manually, but the lifecycle stops short of applying compliant versions.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive