@lystech/core@3.0.125
Lystech Core contains essentials for lystech apps
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection confirms an automatic postinstall mutation and later repository metadata transmission to the package registry. The behavior appears limited to registry synchronization, so the evidence supports a warning rather than a malicious block.
Decision evidence
public snapshot- package.json runs bin/postinstall.cjs automatically during installation.
- The postinstall writes a workflow into the consumer repository; the only shown opt-out is SKIP_LYSTECH_SETUP=true.
- That workflow sends repository owner, name, and ID to the package registry when it runs.
- The workflow is limited to package registry synchronization, and it skips creating a workflow when one already exists.
- The inspected bundle request targets the package-aligned api.lystech.ca service; the scanner's authorization match is consistent with ordinary request headers.
Source & flagged code
9 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 unpkgPackage source references dynamic require/import behavior.
bin/check-pwa.cjsView on unpkg · L3Findings
Affected versions and remediation
This report applies to @lystech/core@3.0.125.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.125 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.