@stacksjs/actions@0.75.373
The Stacks actions.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no install hook, and its root entry registers the action runner and exports library actions. The AWS credential handling and cloud operations belong to the deploy command, while the stacksjs.com match is static email content rather than a credential destination.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the local build; there is no install hook.
- The root entry registers the action runner and exports library actions.
- The deploy code reads AWS credentials from the project environment files and calls the Stacks cloud deployment API as part of deployment.
- The stacksjs.com match is a link in a welcome email template, not a credential destination.
- Loading dist/deploy/index.js runs deployment work at module top level, including a publication check.
- The deploy code reads AWS credentials from project .env files.
Source & flagged code
16 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.373.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.373 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.