check_package
Public safety verdict for ONE package (optionally one version) from CyberXYZ's global threat data: known-malicious releases (always shown in full), advisories, commit-level analysis and version anomalies. Call it BEFORE adding or installing an npm, PyPI, Go or NuGet dependency. decision: block or quarantine = do not install; alert = installable but flagged; allow = ok; unknown = no record, not vetted: ask the user; unverified = the check did not complete: retry, then ask the user. Signing in adds the full install-time verdict (see sign_in_adds).
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"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Package name as published (npm scopes like @org/pkg; Go module path; NuGet id) | |
| version | No | Exact version, e.g. 1.2.3. Omit to check the latest known release. | |
| ecosystem | Yes | Package ecosystem: npm, pypi, go or nuget |