Connection check
verified live · 26h ago
dephealth
Package alive? Verdict with evidence: deprecated, archived, stale or active; plus runtime EOL dates.
Tools
3
GitHub stars
—
Installs / wk
—
Licence
MIT
Transport
streamable-http
Last checked
26h ago
Tools & capabilities
3 toolsRead from the running server on 26h ago.
deps_audit
read-only
manifestpackagestask_context*manifest_kind
Health verdict for every package in a manifest or a list, in one call (≤25 packages): deprecated / archived / stale / active / unknown per package with the latest version, release… Health verdict for every package in a manifest or a list, in one call (≤25 packages): deprecated / archived / stale / active / unknown per package with the latest version, release and push ages, advisory counts and replacements, plus a summary. Use when reviewing a repository's package.json or requirements.txt before an upgrade, an audit or a fork decision.
package_health
read-only
name*versionecosystem*task_context*
Is this package alive? One verdict — deprecated, archived, stale, active or unknown — with the evidence: per-version deprecation from the native registry, yanked/retracted latest r… Is this package alive? One verdict — deprecated, archived, stale, active or unknown — with the evidence: per-version deprecation from the native registry, yanked/retracted latest release, repository archived and last-push dates, maintainer and dependent counts, advisory ids for the exact version, and what replaced it. Use when choosing, pinning or upgrading a dependency in npm, PyPI, crates.io, RubyGems, Go, Maven, NuGet or Packagist.
runtime_eol
read-only
cycleproduct*task_context*