@agentvault/agentvault@0.23.55
⚠ Under reviewEnd-to-end encrypted messaging for AI agents: connects an agent to its owner, rooms and other agents on AgentVault.
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe inspected source shows credential-bearing API requests, but does not establish their effective destinations across callers. I cannot resolve that data flow from the available source evidence, so the result requires manual review; scanner labels alone do not establish an attack.
Decision evidence
public snapshot- The manifest has no install, preinstall, or postinstall hook; its prepublishOnly script runs the build.
- Hub skill loading sends an API key to the supplied apiUrl, but the inspected source does not establish every caller’s apiUrl value or the effective destination.
- Device message polling sends a device JWT to this.config.apiUrl; source inspection did not resolve all configuration callers or destination overrides.
- The manifest identifies AgentVault’s API host as the default API URL, and the inspected hub skill request uses an AgentVault API route.
- The available message polling excerpts use the configured API URL for device message and pending-message endpoints.
Source & flagged code
10 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.jsView on unpkg · L129Findings
Affected versions and remediation
This report applies to @agentvault/agentvault@0.23.55.
See all versions of @agentvault/agentvault for other recorded verdicts.
- Review the evidence and your use of @agentvault/agentvault@0.23.55 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.