@lystech/core@3.0.137
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 3h ago · by lpm-firewall-aiSource inspection found automatic collection and transmission of session-linked application events, including entered checkout email addresses, without an evident opt-in. The destination is the package’s configured Lystech API, so the evidence supports a warning rather than a publish block.
Decision evidence
public snapshot- The browser provider buffers session identifiers, an email address, and user events for transmission.
- The checkout flow records entered email addresses when a form is incomplete or the two email entries differ.
- Buffered events are sent automatically to the configured API endpoint.
- The install hook creates a repository workflow that later contacts the package registry service.
- The provider sends events to its configured Lystech API, consistent with the package’s stated app-provider role.
- The registry workflow only registers a repository when it detects this package in project dependencies.
Source & flagged code
11 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
bin/check-pwa.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @lystech/core@3.0.137.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.137 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.