@trypattern/sdk@0.1.34
AI Security Review
scanned 4d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or concrete malicious behavior. The scanner’s download and execution indicators are consistent with the CLI’s user-invoked project pull and setup features, and its agent-related hints resolve to formatting and ignored-folder references.
Decision evidence
public snapshot- package.json identifies the package entrypoints and contains build and development scripts; no install lifecycle hook is present.
- The `.claude` references in the CLI are part of formatting and ignored-folder lists.
- The pull workflow downloads files for the requested site into a project directory and installs that project’s dependencies; this is a CLI feature, not an install-time action.
- The reviewed SDK modules cover application state, UI components, service access, and server functionality; no concrete attack behavior was established.
- Scanner labels suggested remote code execution and output exfiltration, but inspected source showed project pull and dependency setup rather than a package-triggered payload execution or exfiltration chain.
- The `.claude` references do not show mutation of agent configuration or plugin installation.
Source & flagged code
9 flagged · loading sourcePackage source references child process execution.
dist/cli/publishing.jsView on unpkg · L1Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/cli/publishing.jsView on unpkgFindings
Affected versions and remediation
This report applies to @trypattern/sdk@0.1.34.
See all versions of @trypattern/sdk for other recorded verdicts.
- Review the evidence and your use of @trypattern/sdk@0.1.34 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.