@passioncode-ai/fabric-agent-adapter@0.21.0
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 24d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged configuration location only reads the installed plugin registry. Skill installation is performed by the user-run CLI, so the inspected source does not establish a malicious attack surface.
Decision evidence
public snapshot- package.json exposes the CLI through a bin entry and has no install lifecycle script.
- The flagged configuration check reads Claude's installed plugin registry to detect an existing installation.
- The CLI copies package-provided skills into shared agent skill directories when a user runs it.
- fabric-interop.mjs imports local service helpers and standard Node.js modules.
- The CLI can replace an existing skill copy when run with --force, but this is an explicit user-invoked operation.
Source & flagged code
5 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 · L13Findings
Affected versions and remediation
This report applies to @passioncode-ai/fabric-agent-adapter@0.21.0.
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.21.0 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.