@stacksjs/actions@0.75.343
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe routed clues resolve to package functionality: AWS credentials are loaded for deployment, and the system tray is started through an explicit development API. The manifest has no install hook, and the reviewed code does not show credentials being sent to an unrelated host.
Decision evidence
public snapshot- The package exports its library entry through dist/index.js and has no preinstall, install, or postinstall script; its lifecycle script is prepublishOnly build.
- Importing dist/index.js registers the action runner and re-exports library APIs.
- AWS credentials are read from the project environment files in deployment code, in the context of the deploy workflow.
- The system tray is exposed through an explicit runSystemTrayDevServer call; its deploy action requires confirmation.
- The source paths reviewed show no automatic credential transfer to stacksjs.com or another unrelated host.
- No malicious behavior was identified in the routed package files.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/lint/stx-gate.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @stacksjs/actions@0.75.343.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.343 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.