agent-cards@0.8.1
CLI for managing virtual debit cards for AI agents
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe source establishes an agent integration capability that changes agent instructions when explicitly set up, warranting a warning. The package has no npm install hook, and the inspected workflow includes operator approval rather than a confirmed unconsented control hijack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs an agent setup or engineer setup command.
Impact
An agent may follow the installed instructions and use the package’s capabilities. The inspected source ties this setup to explicit commands and describes operator approval for proposed changes, so no unconsented attack was established.
Mechanism
The CLI writes managed instruction blocks or a skill for supported coding agents; the engineer workflow can run a daemon that communicates with the package’s support service.
AI rationale
The source establishes an agent integration capability that changes agent instructions when explicitly set up, warranting a warning. The package has no npm install hook, and the inspected workflow includes operator approval rather than a confirmed unconsented control hijack.
Evidence
dist/src/commands/agents.jsdist/src/engineer/commands/connect.jsdist/src/engineer/lib/skill.jsdist/src/engineer/lib/snippet.js
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package provides explicit CLI commands that write managed instructions into agent configuration files and a Claude Code skill directory.
- The managed instructions steer coding agents toward the package CLI, while the engineer workflow starts a background daemon to communicate with an AgentCard engineer.
- The package manifest has a publish-time build hook, not an npm install hook; the reviewed agent setup is not triggered by package installation.
Evidence against
- The agent configuration changes are tied to explicit setup commands; no unconsented install-time mutation was established.
- The daemon output says proposed changes require the operator’s acceptance or authorization.
- The global installer is limited to this package and requires confirmation during interactive use.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
Source & flagged code
6 flaggeddist/src/integrate/git.jsView file
1import { execFileSync } from 'child_process';
L2: import { branchNameFor } from './session.js';
High
Child Process
Package source references child process execution.
dist/src/integrate/git.jsView on unpkg · L1dist/src/commands/api.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = agent-cards@0.8.0
matchedIdentity = npm:YWdlbnQtY2FyZHM:0.8.0
similarity = 0.773
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/src/commands/api.jsView on unpkg23if (existsSync(p)) {
L24: return (await import(pathToFileURL(p).href));
L25: }
Medium
Findings
1 Critical5 High4 Medium7 Low
CriticalPrevious Version Dangerous Deltadist/src/commands/api.js
HighChild Processdist/src/integrate/git.js
HighShell
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/src/commands/agents.js
HighRuntime Package Installdist/src/lib/global-install.js
HighSemantic Analysis Limiteddist/src/commands/api.js#virtual:normalized:round1
MediumDynamic Requiredist/src/commands/api.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to agent-cards@0.8.1.
See all versions of agent-cards for other recorded verdicts.
- Review the evidence and your use of agent-cards@0.8.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.