Npm
for LuumenAI
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.
The Npm toolbox
12 tools: 11 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet All Packages Download Count PointGet total npm registry download statistics for all packages for a specified time period.
- ReadGet NPM Download Counts PointGet npm package download statistics for a specified time period.
- ReadGet NPM Package Download Counts Over Date RangeGet download counts for an npm package over a specified date range.
- ReadGet All NPM Packages Download Counts by PeriodGet daily download counts for all npm packages over a specified period.
- ReadGet Registry Changes FeedGet a stream of registry changes for replication purposes.
- ReadGet NPM Registry MetaRetrieves npm registry metadata via meta endpoints.
- ReadGet NPM Package Version Downloads (Last 7 Days)Get download counts for specific versions of a package over the last 7 days.
- ReadQuery Bulk Security AdvisoriesBulk query security advisories for multiple npm packages.
- ReadGet NPM Package MetadataFetch metadata for a specified npm package.
- ReadGet NPM Registry Root MetadataFetches npm registry root metadata including total package count and update sequence.
- ReadSearch NPM PackagesSearch for packages in the npm registry.
- WriteDelete User Token (Legacy)Delete a user authentication token using the legacy endpoint. Approval by default
One prompt, start to finish
What a governed Npm run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as delete user token (legacy). For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Npm to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.