@stacksjs/actions@0.75.269
The Stacks actions.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe forced AI setup call occurs in the upgrade flow rather than an npm install hook, but its configuration effects are not established in the inspected source. This unresolved agent-configuration capability supports a warning, not a confirmed attack finding.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the framework package upgrade flow.
Impact
Agent settings may be refreshed without a separate prompt at this callsite; the affected settings and scope are not shown.
Mechanism
The flow detects providers, including Codex by default, then runs the local setup command with --force.
AI rationale
The forced AI setup call occurs in the upgrade flow rather than an npm install hook, but its configuration effects are not established in the inspected source. This unresolved agent-configuration capability supports a warning, not a confirmed attack finding.
Evidence
dist/upgrade/package-project.jsdist/upgrade/packages.js
Decision evidence
public snapshotAI called this Suspicious at 78.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package declares only a prepublish build hook; it has no install-time script.
- During the upgrade flow, provider detection always includes Codex, and the flow runs the local AI setup command with --force.
- The unresolved runtime operation writes generated route types to the framework auto-imports directory; its caller is route generation.
- The inspected action-runner forwards named actions to this package, while the API dependency exposes fetch and client utilities.
Evidence against
- The AI setup runs through the package upgrade flow, not an npm lifecycle hook; the inspected excerpt does not establish what settings the setup command changes.
- The flagged route-generation operation writes generated project types and does not establish an account action or credential transfer.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
Source & flagged code
4 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
2 High5 Medium6 Low
HighCopied Package Dependency Bridgedist/discover-packages.js
HighSemantic Analysis Limiteddist/pantry-lock.js
MediumSecret Patterndist/github-release.js
MediumDynamic Requiredist/lint/stx-gate.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @stacksjs/actions@0.75.269.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.269 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.