@stacksjs/actions@0.75.382
The Stacks actions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install hook, and the entry point does not automatically load the deployment module. The flagged AWS credential reads support AWS deployment operations, with no evidence of credentials being sent to an unrelated host.
Decision evidence
public snapshot- The manifest exposes dist entry points and lists only a prepublishOnly build hook; there is no install, preinstall, or postinstall hook.
- The main entry point registers the action runner and exports package APIs; it does not import the deployment module.
- Package discovery reads Stacks metadata from project dependencies and writes a generated discovered-packages manifest.
- The deployment module reads AWS credentials from environment variables or project .env files, then uses AWS identity and deployment operations; no credential transfer to stacksjs.com 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.382.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.382 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.