@stacksjs/actions@0.75.383
The Stacks actions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe wildcard export makes the deployment module importable, and that module starts a deployment at top level using AWS credentials. This is a real import-time risk, but the deployment behavior is consistent with the package’s purpose and no malicious credential transfer was identified.
Decision evidence
public snapshot- The wildcard export exposes dist subpaths, including the deploy module, to package consumers.
- Importing dist/deploy/index.js runs deployment code that loads AWS credentials from environment files and calls deployStack at module scope.
- The root entry only registers the action runner; it does not import the deploy module.
- The only lifecycle script is prepublishOnly, which runs the package build.
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.383.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.383 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.