stretchshop@0.7.9
Fast & scalable e-commerce
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe lifecycle and network signals resolve to transparent, package-aligned demo setup without obfuscation or a runtime self-dependency chain. The newly flagged order file contains ordinary invoice and fulfillment behavior, with no concrete attack established by inspected source.
Decision evidence
public snapshot- package.json runs demo/demo.js in base mode after installation and has no runtime self-dependency.
- The flagged order fulfillment file generates invoice PDFs and handles customer emails and order-status changes.
- demo/demo.js clones the fixed StretchShop demo repository.
- Demo copying preserves existing files through clobber: false and COPYFILE_EXCL.
- Downloaded database code runs only when changePath is empty; base installation mode selects the consumer directory when its node_modules exists.
Source & flagged code
4 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references dynamic require/import behavior.
demo/demo.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to stretchshop@0.7.9.
See all versions of stretchshop for other recorded verdicts.
- Review the evidence and your use of stretchshop@0.7.9 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.