@passioncode-ai/fabric-agent-adapter@0.43.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 13d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected agent setup is behind the invoked CLI. The flagged plugin scripts are protocol and identifier helpers; no malicious behavior was established.
Decision evidence
public snapshot- package.json describes this as an installer CLI and defines only a test script; it has no npm install lifecycle hook.
- The launcher checks its arguments in main before performing setup, so package installation alone does not trigger those writes.
- The launcher’s agent setup is a CLI operation; the inspected setup path supports the package’s installer function.
- fabric-identifiers.mjs describes identifier normalization aligned with the Fabric contract.
- fabric-interop.mjs describes reference helpers for the Fabric interop extension.
- fabric-protocols.mjs describes protocol revision and event data helpers.
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 · L14Findings
Affected versions and remediation
This report applies to @passioncode-ai/fabric-agent-adapter@0.43.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.43.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.