@stacksjs/actions@0.75.329
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe inspected credentials and network behavior align with AWS deployment and GitHub release actions. The only lifecycle script builds the package during prepublish, and no unrelated automatic credential transfer was found.
Decision evidence
public snapshot- The only declared lifecycle hook is prepublishOnly, which runs the package build.
- The package entry registers an action runner and exports helpers; its exports do not invoke a deployment action by default.
- The deploy workflow reads AWS credentials from project environment files and passes them into its cloud deployment flow.
- The GitHub release helper looks up GitHub credentials for operations against GitHub.
- The package includes filesystem, environment, dynamic import, and network behavior, but the inspected uses support its framework actions and deployment features.
- The scanner’s AWS-to-stacksjs.com lead was not evidence of credential transmission to that host in the inspected deployment code.
- The discovery helper writes a generated package manifest based on project dependencies when explicitly called.
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.329.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.329 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.