@stacksjs/actions@0.75.390
The Stacks actions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package entrypoint and flagged sources match an actions and deployment toolkit. AWS credentials are read for the deployment workflow, while package discovery and SSL setup perform their stated local tasks; no unrelated collection or harmful automatic action was identified.
Decision evidence
public snapshot- The package exports its action runner and action modules through dist/index.js; the entrypoint sets a runner and re-exports functionality.
- The only lifecycle script is prepublishOnly, which runs the package build.
- Package discovery reads local project manifests and writes a discovered-packages manifest under framework storage.
- The deploy module reads AWS credentials from the environment or project .env files as part of its AWS deployment workflow.
- The inspected entrypoint and flagged files show no automatic credential transfer to an unrelated host.
- The SSL setup changes hosts entries or generates certificates only when its exported setup function is called.
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.390.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.390 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.