agent-cards@0.8.3
CLI for managing virtual debit cards for AI agents
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package sends default runtime telemetry to its own analytics host and documents an opt-out, but it uses the signed-in email as the event identity without disclosing that collection. This is a telemetry disclosure concern; the reviewed source does not show credential theft or another concrete attack.
Decision evidence
public snapshot- Runtime analytics use the signed-in email from local configuration as the event identity and send it with captured events.
- The README describes lifecycle and error telemetry and provides an opt-out, but does not disclose that the signed-in email is used as the analytics identity.
- Telemetry is sent to the package's own host, and users can disable it with documented environment variables.
- The captured properties are limited to lifecycle metadata such as the registered command path and terminal status; the source says command arguments and secrets are excluded.
- Agent instruction files are changed by an explicit `agents add` command; automatic refresh only updates files already carrying the package's managed marker.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/src/integrate/git.jsView on unpkg · L1Package source references dynamic require/import behavior.
dist/src/commands/api.jsView on unpkg · L23Findings
Affected versions and remediation
This report applies to agent-cards@0.8.3.
See all versions of agent-cards for other recorded verdicts.
- Review the evidence and your use of agent-cards@0.8.3 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.