@stacksjs/actions@0.75.222
The Stacks actions.
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe source shows an upgrade-triggered forced agent setup refresh, but not its configuration scope or consent behavior. This supports a warning for agent configuration capability, not a confirmed attack or publish block.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes a framework or dependency upgrade through the upgrade dispatcher.
Impact
The downstream command may change agent configuration during an upgrade; the affected settings and resulting behavior cannot be verified from this package.
Mechanism
The upgrade detects AI providers, including Codex by default, then runs the provider setup command with force enabled.
AI rationale
The source shows an upgrade-triggered forced agent setup refresh, but not its configuration scope or consent behavior. This supports a warning for agent configuration capability, not a confirmed attack or publish block.
Evidence
dist/upgrade/package-project.jsdist/upgrade/packages.js
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest's only lifecycle script is a prepublish build; it defines no install hook.
- The provider detector includes Codex by default and checks project files for other AI providers.
- The upgrade code runs a forced AI setup refresh for every detected provider.
- The upgrade dispatcher runs framework or dependency upgrades only when the corresponding option is supplied.
- The release helper obtains GitHub credentials for publishing releases through the GitHub API.
Evidence against
- This agent-setup path is reached through an explicit upgrade command, not an npm install hook.
- The package does not show the downstream setup command's configuration destinations or consent behavior.
- The GitHub credential use is tied to release publishing for the repository's origin.
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.222.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.222 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.