effect-analyzer@3.6.2
Static analysis for Effect-TS code. Analyze Effect code to extract structure, calculate complexity, and generate visualizations.
AI Security Review
scanned 4d ago · by lpm-firewall-aiInspected source supports the package’s static analysis purpose and does not substantiate the scanner’s credential-redirection claim. The manifest declares no install hook, and the process and filesystem operations found have product-related callers.
Decision evidence
public snapshot- The manifest identifies a static analysis library and CLI and shows build and development scripts, with no install lifecycle hook declared.
- The CLI forwards only named, explicit commands to its TypeScript diagnostic dependency; inspected source did not connect credentials to a remote recipient.
- The analysis and rules modules expose source analysis functions and load ts-morph for parsing; the LSP formats analysis results.
- The public-repository helper clones a fixed list of repositories and runs the analyzer with shell execution disabled.
- Inspected prepared dependency files are TypeScript tooling and runtime modules, consistent with the declared dependencies.
- The static hint alleges credential redirection, but inspected CLI source contains no API-key handling or unrelated credential recipient.
- The CLI and helper use process and filesystem APIs, but the inspected callers show diagnostic forwarding, repository cloning, and analysis output.
Source & flagged code
5 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/rules.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to effect-analyzer@3.6.2.
See all versions of effect-analyzer for other recorded verdicts.
- Review the evidence and your use of effect-analyzer@3.6.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.