@stacksjs/actions@0.75.349
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged AWS credential access is part of the deployment flow, and the GitHub token path targets GitHub's API for release handling. The package declares no install-time hook that would run these operations automatically.
Decision evidence
public snapshot- The only declared lifecycle script is `prepublishOnly`, which runs the build.
- The package entry registers the action runner and exports package APIs; it does not start a deployment or tray server.
- The deployment flow reads AWS credentials for a deployment and passes the configured environment and region to `deployStack`.
- GitHub release handling uses the GitHub API, and the bump flow calls it as part of a release operation.
- The scanner flags credential access and network use, but the inspected AWS credential flow is in the deployment path.
- The package contains a system tray server, but it is exposed through an explicit development action.
- The package has a `prepublishOnly` build script, but no install-time lifecycle hook is declared.
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.349.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.349 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.