Check if a package is still maintained
check_package_maintenanceIs an open-source package still maintained, or is it deprecated, archived or abandoned? Use before adding, upgrading or auditing a dependency. Returns a status (active, slowing, stale, deprecated, archived, inactive, unknown, not_found), a one-sentence verdict, and the evidence: last release date and version, releases in the last 12 months, the registry deprecation flag and message (often names the replacement), the source repository, whether it is archived on GitHub and its last push, and the OpenSSF Scorecard "Maintained" score. Ecosystems: pypi, npm, cargo, go, maven (group:artifact), nuget, rubygems. Live data from deps.dev, PyPI and GitHub, cached 24 h.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"ecosystem": "<ecosystem>",
"name": "<name>"
},
"name": "check_package_maintenance"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Package name as published, e.g. requests, @types/node, serde, github.com/pkg/errors, com.google.guava:guava, Newtonsoft.Json. | |
| ecosystem | Yes | Package ecosystem: pypi, npm, cargo, go, maven, nuget or rubygems (aliases like python, node, rust, java accepted). |