npm Package Metadata — Versions, Licenses & Counts
io.github.kriton-dev/npm-package-metadata
Read latest npm package versions, license tokens and dependency counts
Install surfaces
How npm Package Metadata — Versions, Licenses & Counts runs, per the official MCP registry entry.
- streamable-http
https://mcp.apify.com/?tools=hermeskd/npm-package-metadata
Governed execution
How KLA gates calls to npm Package Metadata — Versions, Licenses & Counts once it is connected.
A published policy defines which npm Package Metadata — Versions, Licenses & Counts actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.
KLA also governs the agents and model providers you already run. See integrations.