@lystech/core@3.0.128
⚠ Under reviewLystech Core contains essentials for lystech apps
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe inspected install hook creates a package registry workflow only for a consumer that already declares this package and asks the user to commit and push it. The selected source for @mantine/core and firebase remains unresolved, so the package needs manual review rather than a malicious verdict based on the available evidence.
Decision evidence
public snapshot- package.json runs bin/postinstall.cjs automatically during installation; the script can create a workflow in the consumer repository.
- The manifest declares @mantine/core and firebase as runtime dependencies, whose selected source was unresolved in the available dependency snapshot.
- The inspected postinstall source gates workflow creation on the consumer already declaring this package and tells the user to commit and push the generated workflow.
- The visible workflow registers repository name and ID with the package registry API; the source does not show it sending the GitHub token to that API.
- The bundled runtime sets its API client base URL to api.lystech.ca and attaches stored authentication headers to that client. These inspected behaviors did not establish credential theft.
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.128.
See all versions of @lystech/core for other recorded verdicts.
- Review the evidence and your use of @lystech/core@3.0.128 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.