@stacksjs/actions@0.75.346
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe root import only configures the action runner and exposes functions. The flagged credential use is within the deployment command, the system tray is started only through its dedicated action, and the only lifecycle script is a prepublish build.
Decision evidence
public snapshot- The root export initializes the action runner and re-exports package functions; it does not itself invoke a deployment or tray action.
- The system-tray barrel exports a function that runs the tray action on request; it does not import the tray server module.
- The prepublishOnly script runs a build and is not an install hook.
- The AWS credential handling is inside the deploy command, which uses AWS SDK clients for deployment operations.
- Package discovery writes a project manifest only when its exported discovery function is called.
- The package contains network-capable deployment and GitHub release utilities, but their use is tied to explicit actions.
- The system tray starts a local server when its dedicated module is invoked, but that module is not imported by the dev barrel.
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.346.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.346 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.