registry / @stacksjs/actions / 0.75.257
@stacksjs/actions@0.75.257
The Stacks actions.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe source shows a forced AI setup command within the explicit package-upgrade flow, while the resulting configuration changes cannot be resolved from this snapshot. The manifest has no install lifecycle hook, so this is a warning rather than a publish block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A caller invokes `upgradeStacksPackages` for a project.
Impact
Agent configuration may be forced or refreshed; the exact files and overwrite scope are not shown in this package snapshot.
Mechanism
The provider detector always includes Codex, adds providers based on project markers, then the upgrade flow runs `./buddy setup:ai <provider> --force` from the project root.
AI rationale
The source shows a forced AI setup command within the explicit package-upgrade flow, while the resulting configuration changes cannot be resolved from this snapshot. The manifest has no install lifecycle hook, so this is a warning rather than a publish block.
Evidence
dist/upgrade/package-project.jsdist/upgrade/packages.js
Decision evidence
public snapshotAI called this Suspicious at 81.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The provider detector includes Codex by default and detects other providers from project markers.
- The package upgrade flow runs `./buddy setup:ai <provider> --force` in the project root for every detected provider; no separate consent check appears at that call site.
- The package source shows this setup call inside the explicit `upgradeStacksPackages` flow, but does not show the setup command’s implementation or the exact configuration files it writes.
- The runtime operation hint builds generated route type text from collected routes; it is unrelated to agent setup.
- The inspected API fetcher sends requests to the supplied URL with client headers and body; the cited excerpt does not show a fixed unrelated recipient.
Evidence against
- The manifest lists `prepublishOnly` for building and has no npm install lifecycle hook, so this behavior is not activated by package installation.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEval
Source & flagged code
5 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
3 High5 Medium6 Low
HighCopied Package Dependency Bridgedist/discover-packages.js
HighSemantic Analysis Limiteddist/pantry-lock.js
HighPrevious Version Dangerous Deltadist/project-scripts.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.257.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.257 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.