Check npm package metadata, advisories, and download trends, then revoke a stale token.
Connect npm and your agent can answer dependency questions from the registry itself. Look up package metadata and version history, bulk-query security advisories across a dependency list, and compare download counts over a date range. Token cleanup runs as a previewed, approved step, and the whole session is audited.
12 tools: 11 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Npm run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — delete user token (legacy) — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Npm — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.