@trypattern/sdk@0.1.15
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged CLI behavior is tied to explicit project commands. The inspected source does not establish credential disclosure to an unrelated recipient or another concrete attack.
Decision evidence
public snapshot- package.json exposes a CLI and library exports, with no install lifecycle hook.
- The CLI checks for a Pattern project before running project commands.
- Pulling a project requires an explicit CLI command and a signed-in session.
- Saved cookies are associated with the selected dashboard; publishing requests send them to that dashboard.
- The cited runtime files implement state, UI, platform, database, authentication, and theme utilities.
- Scanner labels mention download execution, command output, and dynamic loading, but inspected source shows project pull and setup flows rather than an automatic install-time trigger.
- The inspected CLI setup code checks before replacing an existing global shim and refuses to overwrite an unrecognized file.
Source & flagged code
8 flagged · loading sourcePackage source references child process execution.
dist/cli/publishing.jsView on unpkg · L1Package source references dynamic require/import behavior.
dist/cli/starter.jsView on unpkg · L79Findings
Affected versions and remediation
This report applies to @trypattern/sdk@0.1.15.
See all versions of @trypattern/sdk for other recorded verdicts.
- Review the evidence and your use of @trypattern/sdk@0.1.15 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.