@stacksjs/actions@0.75.342
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package has no install hook, and its import-time behavior only registers the action runner. The flagged filesystem, network, credential and server behavior is consistent with the package’s framework functions and is invoked through requested actions.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the build; there is no install hook.
- Importing the main entry registers the action runner and re-exports the package API.
- Action files are loaded by the runner when an action is requested; the system tray starts through an explicit dev-server function.
- Package discovery is an exported function that reads project dependency metadata and writes a discovered-packages manifest.
- GitHub token lookup is paired with GitHub API use, and AWS credentials are read from project environment files for deployment.
- The package contains filesystem access, subprocess execution, network calls and environment-variable reads, which fit its framework and deployment functions.
- The system tray server has no authentication, but it is started only through an explicit system-tray dev action.
- The source includes deploy-time AWS credential handling, but the inspected code shows no unrelated credential destination.
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.342.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.342 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.