@lystech/core@3.0.109
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe package automatically writes a consumer GitHub workflow during postinstall, creating unresolved installation-time mutation risk despite the package-aligned registry purpose and skip guards. The inspected source does not substantiate the scanner’s credential-exfiltration claim.
Decision evidence
public snapshot- The manifest runs bin/postinstall.cjs automatically after installation.
- The hook proceeds when the consumer project lists @lystech/core and no existing workflow is present; it also supports an environment skip flag.
- The hook creates a GitHub Actions workflow in the consumer project without an explicit setup command.
- The generated workflow registers the project in the package registry; the inspected excerpt shows it uses the GitHub repository context.
- The UMD bundle excerpt reads Firebase defaults from environment or browser cookies, with no evidence in that excerpt of sending them elsewhere.
- The postinstall hook skips when run inside @lystech/core itself and skips projects that do not depend on the package.
- The inspected setup workflow uses GitHub repository context and the GitHub API, consistent with package registry setup.
- The flagged bundle excerpt alone does not establish credential exfiltration.
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 unpkgFindings
Affected versions and remediation
This report applies to @lystech/core@3.0.109.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.109 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.