@passioncode-ai/fabric-agent-adapter@0.35.1
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 18d ago · by lpm-firewall-aiSource inspection found no npm lifecycle hook or malicious behavior. The flagged configuration access reads plugin installation state, while skill copying and service setup occur through explicit user-invoked functionality.
Decision evidence
public snapshot- package.json defines a test script and CLI binary, with no npm install lifecycle script.
- The flagged integration code reads Claude's installed-plugin record to decide whether to skip a shadowing skill copy; it does not change that record.
- The CLI copies packaged skills into the selected skills directory only when invoked, and skips existing entries unless forced.
- The pack, sign, and verify helper is imported only when one of those commands is supplied.
- The identifier helper normalizes and compares identifiers without system or network actions.
- The service helper's systemd setup is an explicit function for a requested user unit, not an npm lifecycle action.
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.35.1.
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.35.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.