@aifinpay/agent@2.11.1
AiFinPay SDK for global Agent Passport identity and route-verified AIFP-1/AIFP-2 settlement for autonomous AI agents.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged wallet transfer behavior belongs to the package’s payment SDK and requires an explicit caller invocation. The manifest has no install hook, and the inspected entrypoint only exports the bridge API rather than running it automatically.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the build; no install hook is declared.
- The package exports bridge operations as public APIs; the entrypoint does not invoke them automatically.
- Bridge execution is an explicit method that submits a transaction from a previously fetched quote.
- Before signing, bridge execution checks the source chain and rejects unquoted native value or excessive gas.
- The bridge quote uses the agent’s address by default, with an optional caller-supplied destination.
- The package is a payment SDK, so wallet signing and cross-chain transfers match its stated purpose.
- Bridge operations contact LiFi at https://li.quest/v1, the documented bridge quote and status service.
Source & flagged code
4 flaggedSource uses private key material to transfer cryptocurrency funds.
dist/unifiedAgent.jsView on unpkg · L16Findings
Affected versions and remediation
This report applies to @aifinpay/agent@2.11.1.
See all versions of @aifinpay/agent for other recorded verdicts.
- Review the evidence and your use of @aifinpay/agent@2.11.1 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.