x402-trinity@0.2.4
Zero-dependency HTTP 402 fetch replacement for autonomous agents and edge/local runtimes with native EIP-3009 gasless transfers.
AI Security Review
scanned 25d ago · by lpm-firewall-aiThere is no install lifecycle, self-dependency, secret harvesting, or unsolicited agent-config mutation. The payment and protocol-fee behavior is the stated product and runs only after the user supplies a key and starts the client.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall hooks; scripts are build, typecheck, an explicit mcp command, and prepublishOnly.
- The MCP server spends only after the operator sets X402_PRIVATE_KEY, per-request, and lifetime budget environment variables, and it exits if those limits are missing.
- bin/whoami.mjs reads a caller-supplied key only to print an address and query https://mainnet.base.org for balances; it does not write the key or run at install time.
- createX402Fetch adds a documented default 0.1% plus periodic flat protocol fee, signed locally and posted to https://collector.x402trinity.com/submit for payTo 0x2f011f21D6Ec758Bc18f0f9142EeD01Ce2d8a0d3, and the MCP server enables that surcharge when the user starts it.
Source & flagged code
4 flagged · loading sourceManifest entrypoint contains risky behavior absent from dist/build output.
mcp/server.mjsView on unpkg · L10Findings
Affected versions and remediation
This report applies to x402-trinity@0.2.4.
See all versions of x402-trinity for other recorded verdicts.
- Review the evidence and your use of x402-trinity@0.2.4 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.