@stacksjs/actions@0.75.369
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package metadata and entry point are consistent with the Stacks actions package, and the flagged AWS credential read occurs in deployment code. The reviewed excerpts show no unrelated credential transport or harmful automatic behavior.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the package build.
- The main entry registers the action runner and exports package functionality; the excerpt shows no unrelated import-time action.
- Package discovery reads project dependencies and Stacks metadata, then writes a discovered-packages manifest when explicitly called.
- Deployment code reads AWS credentials from project environment files as part of its deployment flow.
- The deployment code handles cloud infrastructure operations, consistent with this package’s actions and framework purpose.
- The scanner’s credential pointer does not by itself establish that credentials are sent to an unrelated host.
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.369.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.369 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.