registry / @stacksjs/actions / 0.75.423
@stacksjs/actions@0.75.423
The Stacks actions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package’s lifecycle script only builds the package, and its main entry registers an action runner without starting deployment. The flagged AWS credential reads are part of the deployment workflow, and the source did not show credentials being sent to stacksjs.com or another unrelated collector.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Importing the main entry registers the action runner; deployment behavior is in a separate deployment module.
Impact
No malicious impact identified from the inspected source.
Mechanism
The deployment workflow reads AWS credentials for AWS deployment operations. No source evidence showed those credentials being sent to an unrelated host.
AI rationale
The package’s lifecycle script only builds the package, and its main entry registers an action runner without starting deployment. The flagged AWS credential reads are part of the deployment workflow, and the source did not show credentials being sent to stacksjs.com or another unrelated collector.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script is prepublishOnly, which runs the package build; there is no install, preinstall, or postinstall hook.
- The main entry registers runAction with the action runner and re-exports package APIs; it does not invoke deployment code.
- The action-runner bridge loads @stacksjs/actions only when a named action is requested and no runner is registered.
- The AWS credential reads occur in the deployment workflow, which proceeds to deployStack; no transmission of those credentials to stacksjs.com was found.
Evidence against
- Scanner similarity and semantic-analysis-limit alerts are leads, not source evidence of malicious behavior.
- The AWS credential and stacksjs.com matches are not a credential exfiltration chain: the domain appears in welcome-email content, while deployment uses AWS clients.
- The runtime dependency bridge is a lazy action-dispatch mechanism, not an automatic credential or network operation.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
Source & flagged code
16 flaggeddist/github-release.jsView file
5patternName = generic_password
severity = medium
line = 5
Medium
dist/lint/stx-gate.jsView file
1import{existsSync}from"node:fs";import{join}from"node:path";import process from"node:process";import{Glob}from"bun";export const DEFAULT_STX_LINT_CONFIG={stxGlob:"resources/**/*.st...
L2: `).forEach((line,i)=>{re.lastIndex=0;if(!re.test(line))return;if(ignore){ignore.lastIndex=0;if(ignore.test(line))return}hits.push(`${f}:${i+1} ${line.trim().slice(0,90)}`)})}retur...
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/lint/stx-gate.jsView on unpkg · L1dist/discover-packages.jsView file
Findings
14 High5 Medium6 Low
HighCopied Package Dependency Bridgedist/discover-packages.js
HighSemantic Analysis Limiteddist/pantry-lock.js
HighKnown Malware Source Similaritydist/setup/ssl.js
HighKnown Malware Source Similaritydist/deploy/index.js
HighKnown Malware Source Similaritydist/dev/system-tray.js
HighKnown Malware Source Similaritydist/project-scripts.js
HighKnown Malware Source Similaritydist/upgrade/framework-utils.js
HighKnown Malware Source Similaritydist/upgrade/framework.js
HighKnown Malware Source Similaritydist/dev/dashboard-supervisor.js
HighKnown Malware Source Similaritydist/make.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to @stacksjs/actions@0.75.423.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.423 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.