@retailrocketgroup/retailrocket-edit.product-back-in-stock-vue-email-template-render@11.0.433360
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe available source describes a Vue email-template editor and its configured save flow, with no install hooks or suspicious credential collection found. Network requests use page-supplied service URLs for the editor's feature; the scanner's bundle fingerprint alone does not establish malicious behavior.
Decision evidence
public snapshot- The manifest declares no lifecycle scripts, executable bin, or entry-point metadata; it identifies a public package.
- The source initializes a Vue email-template editor using page-provided partner, proxy, and editor URLs and anti-forgery values.
- Saving submits the edited template JSON and partner ID through the editor BFF client.
- The page bundle loads from the package's own /assets/index.js path.
- The flagged bundle contains ordinary fetch-based API client code that posts to a configured base URL with anti-forgery headers.
- The source's reset and exit actions are tied to explicit editor callbacks and page-provided URLs.
Source & flagged code
6 flaggedSource fingerprint signature matches a known malicious package signature; route for source-aware review.
dist/assets/index.jsView on unpkgPackage contains source files above the normal full-analysis size ceiling.
dist/assets/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @retailrocketgroup/retailrocket-edit.product-back-in-stock-vue-email-template-render@11.0.433360.
See all versions of @retailrocketgroup/retailrocket-edit.product-back-in-stock-vue-email-template-render for other recorded verdicts.
- Review the evidence and your use of @retailrocketgroup/retailrocket-edit.product-back-in-stock-vue-email-template-render@11.0.433360 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.