Package Health
package_healthAssess npm, PyPI, or Cargo package trust before adoption: check release recency, deprecation, license, maintainers, dependencies, and security advisories.
Instructions
A composite trust/health check for a package an agent is considering: latest-release recency, deprecation status, license present, maintainer count, dependency count, and any known security advisories (via deps.dev). Returns a summary an agent can act on. Ecosystems: npm, pypi, cargo.
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": "package_health"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Exact package name as published in that registry, e.g. express for npm, requests for pypi, serde for cargo. | |
| ecosystem | Yes | Package registry to look in. One of: npm, pypi, cargo. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| license | No | ||
| verdict | No | ||
| concerns | No | ||
| deprecated | No | ||
| provenance | No | Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be older than served_at. | |
| repository | No | ||
| has_license | No | ||
| maintainers | No | ||
| advisory_ids | No | ||
| last_release | No | ||
| latest_version | No | ||
| known_advisories | No | ||
| days_since_release | No | ||
| actively_maintained | No |