unripe
Related Servers
Alternatives to unripe
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceChecks npm and PyPI packages for outdated versions, deprecation status, and breaking changes with cited sources, enabling AI agents to verify dependency freshness.16 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables an AI agent to parse project lockfiles (npm, pnpm, Yarn, uv, Poetry, requirements.txt, Cargo, go.sum) and query OSV.dev to find known vulnerabilities in locked versions, transitive dependencies included, then produce minimal upgrade plans with breaking-change flags, cleanliness re-checks, and the parent dependency responsible. It also lists outdated packages and explains individual advisories, all read-only with no API key required.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to check package names and versions for allow/warn/deny verdicts, scan project lockfiles for known-malicious packages and critical advisories, and suggest safe versions across npm, PyPI, crates.io, and Go before manifests are edited.36 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.71MIT
TDQS
Scored across 3 tools
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.
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.
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.
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.