@lystech/core@3.0.130
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package's postinstall creates a consumer workflow that performs recurring registry synchronization without an affirmative setup step. Because the inspected payload is repository metadata and the behavior is package-related, the evidence supports a warning rather than a publish block.
Decision evidence
public snapshot- package.json runs bin/postinstall.cjs during installation.
- The postinstall checks whether the consumer project declares @lystech/core, then creates a workflow that runs on pushes to main or master.
- The workflow queries GitHub for the repository ID and sends the package name, owner, repository name, and ID to the Lystech registry endpoint.
- The postinstall writes the workflow into the consumer project's .github/workflows directory.
- The workflow is for syncing @lystech/core package registration, and the inspected payload contains repository identifiers rather than credentials.
Source & flagged code
10 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.130.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.130 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.