@stacksjs/actions@0.75.328
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package exposes framework action helpers and a separate AWS deployment flow, while its only lifecycle script builds the package. The AWS credentials found in the deployment module are used for AWS operations, and no unrelated credential exfiltration or malicious automatic behavior was identified.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the package build.
- The primary entry point registers the action runner and exports action helpers; it does not import the deployment module.
- The deployment module reads AWS credentials from the project environment files and then invokes AWS deployment operations, consistent with its purpose.
- Package discovery reads installed package metadata and writes a generated discovered-packages manifest.
- The deployment module reads AWS access keys, but the reviewed flow uses them for AWS operations rather than sending them to stacksjs.com.
- The package includes network and filesystem capabilities for deployment and project tooling.
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.328.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.328 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.