@stacksjs/actions@0.75.320
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe inspected package entry and flagged source show ordinary Stacks framework operations. Credential access and release publishing occur in explicit deployment or release workflows, with no evidence of automatic exfiltration or unrelated actions.
Decision evidence
public snapshot- The package defines build and typecheck scripts plus prepublishOnly, with no install, preinstall, or postinstall hook.
- The main entry wires the action runner and exports package functions; it does not call the flagged discovery or deployment routines at import time.
- AWS credentials are read from project environment files inside the deployment path.
- Package discovery reads project manifests and writes a discovered-packages manifest under the framework storage path.
- The package includes GitHub release functionality that can obtain a GitHub token and publish a release when invoked.
- The deployment module reads AWS credentials, but the reviewed source places that behavior in the deployment path rather than package installation or main-entry import.
Source & flagged code
4 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.320.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.320 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.