@passioncode-ai/fabric-agent-adapter@0.48.2
Create Fabric-compatible agents, run them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract. This package is the installer CLI.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the agent-directory writes occur through an explicitly invoked installer CLI. The scanner’s flagged source paths contain contract validation or verification logic, so the inspected evidence does not establish an attack.
Decision evidence
public snapshot- package.json defines only a test script and exposes the installer as a CLI command.
- The CLI copies packaged skills into the user’s agent skills directory when invoked; it has no install lifecycle hook.
- The inspected plugin check reads Claude’s installed plugin manifest to avoid shadowing an existing plugin.
- The flagged identifier, protocol, and estate files contain contract validation and cryptographic verification code.
Source & flagged code
6 flaggedManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
bin/fabric-agent-adapter.jsView on unpkgPackage source references dynamic require/import behavior.
bin/fabric-agent-adapter.jsView on unpkg · L14Findings
Affected versions and remediation
This report applies to @passioncode-ai/fabric-agent-adapter@0.48.2.
See all versions of @passioncode-ai/fabric-agent-adapter for other recorded verdicts.
- Review the evidence and your use of @passioncode-ai/fabric-agent-adapter@0.48.2 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.