@stacksjs/actions@0.75.323
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package's only lifecycle hook builds before publishing, and its import-time action-runner setup is consistent with its purpose. The AWS credential flow is in the deployment helper, while the stacksjs.com match is email-template content; no automatic credential exfiltration or unrelated action was found.
Decision evidence
public snapshot- The only declared lifecycle hook is prepublishOnly, which runs the package build.
- The root import configures the action runner and re-exports package APIs.
- The deployment helper loads AWS credentials and uses them in the framework deployment flow.
- The GitHub release helper obtains GitHub credentials for GitHub release operations.
- The stacksjs.com reference appears in a welcome email template, not as an AWS credential destination.
- Deployment code can read AWS credentials from environment variables or project .env files.
- The package includes network and filesystem operations for deployment, release publishing, and framework tasks.
Source & flagged code
4 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.323.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.323 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.