@trypattern/sdk@0.1.30
AI Security Review
scanned 4d ago · by lpm-firewall-aiSource inspection found no install hook, credential transfer to an unrelated recipient, or agent configuration mutation. The scanner's download and execution hint maps to the user-invoked project pull workflow.
Decision evidence
public snapshot- package.json identifies the CLI entrypoint and lists development scripts; it declares no install lifecycle hook.
- The app pull command is explicitly invoked. It downloads project files, installs that project's dependencies, and runs its setup.
- Saved CLI cookies are selected by the configured dashboard and sent to that same dashboard. The default is Pattern's service; an environment variable can select another dashboard.
- The flagged .claude locations are a formatting path and an empty-folder ignore entry; they do not show agent configuration changes.
- The other required paths inspected contain UI, state, date, booking, service, access-control, and theme utilities; their inspected excerpts show no attack behavior.
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.30.
See all versions of @trypattern/sdk for other recorded verdicts.
- Review the evidence and your use of @trypattern/sdk@0.1.30 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.