@lystech/core@3.0.127
⚠ Under reviewLystech Core contains essentials for lystech apps
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe inspected workflow is package-specific and its push-triggered disclosure requires a later repository event after the generated file is committed. Full review remains unresolved because some declared runtime dependency source could not be verified, so the package cannot be cleared from this inspection alone.
Decision evidence
public snapshot- The manifest runs a postinstall setup script; it skips if the opt-out is set or the consuming project does not declare this package.
- The hook writes a registry-sync workflow that runs on later pushes or manual dispatch and sends repository identity and package presence to the package registry endpoint.
- The reviewed setup code does not establish a direct network send during package installation; full runtime dependency behavior remains unresolved.
- The generated workflow registers this package and only activates after a later repository event.
- The hook prints instructions to commit and push the generated workflow, providing a user action before push-triggered disclosure.
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.127.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.127 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.