@stacksjs/actions@0.75.387
The Stacks actions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install-time hook, and the package entry point performs action-runner registration before exporting its functionality. The flagged AWS credential handling is part of deployment code that calls AWS services; the inspected source does not show credentials sent to an unrelated host.
Decision evidence
public snapshot- The package identifies itself as @stacksjs/actions, and its entry point wires the action runner before exporting action helpers.
- The only lifecycle hook is prepublishOnly, which runs the build; there is no install hook.
- The deploy module reads AWS credentials from environment variables or project .env files for its deployment workflow.
- The AWS client is used for a CloudFront cache invalidation, consistent with deployment functionality.
- SSL setup generates local certificates and writes them under the user's home directory when that setup function is invoked.
- The root entry point configures the action runner at import time; the inspected code does not show unrelated collection or transmission.
- The credential use appears in deployment code and targets an AWS service operation; no foreign credential collector was identified.
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.387.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.387 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.