@stacksjs/actions@0.75.360
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package’s credential handling is tied to AWS deployment and GitHub release workflows, with no evidence of unrelated credential exfiltration or harmful automatic behavior. The scanner’s stacksjs.com match appears in welcome email content rather than a network request.
Decision evidence
public snapshot- The package exports its built action API and declares only a prepublish build script; it has no install lifecycle hook.
- Importing the main entry registers the action runner and exports package functionality.
- The deployment code reads AWS credentials from project environment files as part of its AWS deployment workflow.
- GitHub credentials are requested for github.com, and release requests target the GitHub repository derived from the project origin.
- The flagged stacksjs.com matches are email content, not credential transport.
- No unrelated credential transmission, concealed code, or install-time network behavior was identified.
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.360.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.360 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.