paidwithtab@2.4.0
Give your agents spending power. tab prices any HTTP API in a JSON spec and gets it paid per request over HTTP 402 and x402, spending capped by signed mandates, settled in USDG on Robinhood Chain. Zero runtime dependencies.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged wallet transfer occurs in the explicitly invoked fund command and requires a source key and recipient. Client-side payment handling is part of the package’s stated purpose and applies mandate, spending, and token checks.
Decision evidence
public snapshot- The package exports its client library; the CLI is a separate executable entry point.
- The fund command requires an explicit source key and recipient before sending funds.
- Automatic challenge payments check mandate expiry, allowed realm, and spending limits.
- EVM payments require a mandate owner and a token recognized by the client.
Source & flagged code
4 flaggedSource uses private key material to transfer cryptocurrency funds.
dist/src/cli.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to paidwithtab@2.4.0.
See all versions of paidwithtab for other recorded verdicts.
- Review the evidence and your use of paidwithtab@2.4.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.