Is this dependency still maintained? Scores npm, PyPI packages and GitHub repos 0-100.
MCPpedia last refreshed this data
io.github.orcsnren/pkg-health-mcp is an MCP server that is this dependency still maintained? Scores npm, PyPI packages and GitHub repos 0-100. Its tool list has not been published yet over stdio and http, requires no API key, and scores 59/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"pkg-health": {
"env": {
"GITHUB_TOKEN": "github_pat_xxx"
},
"args": [
"-y",
"pkg-health-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Is this dependency still maintained? Scores npm, PyPI packages and GitHub repos 0-100.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'pkg-health-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked pkg-health-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in developer-tools
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Manage Supabase projects — databases, auth, storage, and edge functions
MCP server for using the GitLab API
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
MCP Security Weekly
Get CVE alerts and security updates for io.github.orcsnren/pkg-health-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Is this dependency still maintained? Find out before you install it.
pkg-health-mcp scores npm packages, PyPI packages and GitHub repositories from 0 to 100 for maintenance health. It combines release and commit activity, active maintainers, issue response times, download trends, OpenSSF Scorecard and license into an A–F grade and a plain-language list of risks.
Use it three ways, all built on the same engine:
$ npx -y pkg-health-mcp scan package.json
F 10/100 request@2.88.2 [npm]
10 Recent activity last release 2444d ago
5 Maintainer diversity 0 active committer(s) in the last 12 months
10 Issue responsiveness median 113.2d to first maintainer response, 38% answered (8 issues)
65 Download trend 171.5M downloads in last 90d (-5% vs previous 90d)
34 OpenSSF Scorecard 3.4/10
100 License Apache-2.0 (permissive)
! Deprecated: request has been deprecated, see https://github.com/request/request/issues/3142
! No release in 6+ years
! No commits in the last 12 months
! 62% of recent issues got no maintainer response
F 10/100 left-pad@1.3.0 [npm]
! Deprecated: use String.prototype.padStart()
! Source repository is archived
A 99/100 express@5.3.0 [npm]
100 Recent activity last release 12d ago, last commit 4d ago
100 Maintainer diversity 42 active committer(s) in the last 12 months
100 Issue responsiveness median 0.2d to first maintainer response, 87% answered (53 issues)
100 Download trend 1.6B downloads in last 90d (+22% vs previous 90d)
85 OpenSSF Scorecard 8.5/10
100 License MIT (permissive)
A typical project pulls in hundreds of open-source packages. Some of them are quietly abandoned: no releases for years, one maintainer who moved on, issues piling up unanswered. When a vulnerability shows up in one of those, nobody fixes it.
Checking this by hand means opening each package's GitHub page and reading commit dates, issue lists and contributor graphs. Nobody does that for every dependency, and AI coding assistants never do it: they happily suggest whatever library was popular in their training data, including ones deprecated years ago.
pkg-health-mcp makes that check a single tool call, so: