@lystech/core@3.0.102
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe automatic postinstall mutation adds consumer CI automation and sends repository metadata to the package service, creating a real but unresolved install-time risk. The inspected behavior does not establish a concrete attack or unrelated credential exfiltration, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- package.json runs bin/postinstall.cjs automatically on install.
- The postinstall hook can create a workflow in the consumer repository without an explicit setup command; it skips creation only when disabled, when the package is absent from dependencies, or when the workflow already exists.
- The generated workflow uses the repository's GitHub token to query GitHub, then sends repository identifiers to the package registry endpoint.
- The bundle's stored auth values are attached to a client with a fixed api.lystech.ca base URL.
- The postinstall hook has skip conditions and preserves an existing workflow.
- The inspected bundle sends its stored credentials to the package's fixed API host, with no evidence here of forwarding them to an unrelated recipient.
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.102.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.102 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.