agentic-payments@0.1.17
VERIFIED· startup onlyPublisher claims: "Payment authorization for AI agents: Ed25519 spending mandates, multi-agent consensus, RFC 9421 signed payment requests, and an MCP server." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- second launch with the clock 45 days ahead · server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- ruv.io (its own)Also rustup.rs — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable and talks to ruv.io, its own; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 46 s · 3 scenarios · 0 deviationsStatic findings
console.log(chalk.white(output) + '\n');Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(chalk.white(output) + '\n');Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(chalk.white(output) + '\n');Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(chalk.blue(`\n✓ Mandate saved to: ${options.output}\n`));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(chalk.white(output));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(chalk.blue(`\n✓ Identity saved to: ${options.output}`));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* NPX Cache Cleanup ScriptFix: Pin versions and sources; vendor anything fetched at install time.console.log(chalk.blue(`\n✓ Signed mandate saved to: ${options.output}\n`));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// Clean up npx cache on startup to prevent ENOTEMPTY errorsFix: Pin versions and sources; vendor anything fetched at install time.console.log(chalk.blue(`\n✓ Mandate saved to: ${options.output}`));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(chalk.blue(`\n✓ Signed mandate saved to: ${options.output}\n`));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.import { HttpMCPServer } from './transports/http.js';Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.* Fixes ENOTEMPTY errors on remote installs by cleaning up stale npx cacheFix: Pin versions and sources; vendor anything fetched at install time.// Clean up npx cache on startup to prevent ENOTEMPTY errorsFix: Pin versions and sources; vendor anything fetched at install time.console.log(chalk.white(output));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* This script addresses the common npx caching issue where:Fix: Pin versions and sources; vendor anything fetched at install time.echo "Install: npx agentic-payments@latest"Fix: Pin versions and sources; vendor anything fetched at install time.git tag -a "v${NEW_VERSION}" -m "Release v${NEW_VERSION}: NPX cache fix improvements"Fix: Pin versions and sources; vendor anything fetched at install time.- Enhanced npx cache cleanup to prevent ENOTEMPTY errors in remote environmentsFix: Pin versions and sources; vendor anything fetched at install time.git commit -m "chore(release): v${NEW_VERSION} - NPX cache fix improvements" || trueFix: Pin versions and sources; vendor anything fetched at install time.console.log('[agentic-payments] Cleaning npx cache to prevent ENOTEMPTY errors...');Fix: Pin versions and sources; vendor anything fetched at install time.# Validates npx cache fix in Docker, then publishes point releaseFix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for agentic-payments@0.1.17 as of 5d ago. This is the package itself, not its dependencies.