@stacksjs/actions@0.75.389
The Stacks actions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package has no install hook beyond building for publication. The flagged AWS credential handling is used by the deployment implementation, and the source provides no evidence that credentials are sent to an unrelated host.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly running the package build.
- The main entry initializes the action runner and exports package APIs.
- The deployment module reads AWS credentials from environment variables or project .env files for deployment.
- The deployment flow calls AWS STS and deployStack to deploy the configured project.
- The AWS credential use is tied to the package's deployment functionality; no unrelated credential destination was identified.
- The stacksjs.com references found in the deployment source are welcome-email content, not evidence of a credential transport.
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.389.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.389 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.