@lystech/core@3.0.138
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 7h ago · by lpm-firewall-aiThe install hook makes a persistent consumer CI configuration change without an affirmative setup step, so the package warrants a warning. The inspected registry flow is package-related and does not establish a concrete malicious exfiltration attack.
Decision evidence
public snapshot- The manifest runs bin/postinstall.cjs during installation. The hook can be skipped by an environment variable, but otherwise proceeds when the consumer project declares @lystech/core.
- The hook writes a GitHub Actions workflow into the consumer project without asking first. On later pushes or manual dispatch, that workflow reads repository identity and sends the package name, owner, repository, and repository ID to the package registry service.
- The bundle’s stored auth values are attached to requests through its service client; the inspected default API host is api.lystech.ca. This does not establish credential disclosure to an unrelated recipient.
- The setup is directed at registering consumer projects for the package’s update and registry service. The inspected code does not show secrets being sent to that service.
- The postinstall hook skips projects without a package manifest, projects that do not declare @lystech/core, projects where the opt-out is set, and projects where the workflow already exists.
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.138.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.138 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.