registry / @stacksjs/actions / 0.75.236
@stacksjs/actions@0.75.236
The Stacks actions.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe upgrade command performs a forced, package-owned agent setup refresh that may change project instructions, warranting a warning. The package has no inspected npm install hook for this behavior, and source does not establish a concrete malicious attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the project upgrade command and its update path reaches the AI setup refresh.
Impact
Project agent instructions or configuration may be created or changed without a separate setup prompt.
Mechanism
The updater detects providers and invokes their setup command with a force option; the package identifies AGENTS.md as canonical after an update.
AI rationale
The upgrade command performs a forced, package-owned agent setup refresh that may change project instructions, warranting a warning. The package has no inspected npm install hook for this behavior, and source does not establish a concrete malicious attack.
Evidence
dist/upgrade/packages.jsdist/upgrade/package-project.jsdist/upgrade/package-project.d.tsAGENTS.md
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package refreshes detected AI provider setup with a forced command during an upgrade.
- Codex is included by default, and the package describes its canonical AGENTS.md as present after an update.
Evidence against
- The manifest has a prepublishOnly build script; this behavior is reached through an upgrade command, not an npm install hook.
- The inspected source does not establish the setup command’s exact write scope or any credential transfer, exfiltration, or other attack.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
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/release-preflight.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.236.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.236 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.