registry / @stacksjs/actions / 0.75.255
@stacksjs/actions@0.75.255
The Stacks actions.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe upgrade flow performs forced setup for detected AI providers, but the inspected source does not resolve the setup's effects or consent behavior. This supports a warning, not a finding of malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the package upgrade flow.
Impact
The setup may refresh agent integration configuration; its effects and consent behavior are unresolved in the inspected source.
Mechanism
The upgrade flow detects providers and invokes the project buddy setup command for each one with a force flag.
AI rationale
The upgrade flow performs forced setup for detected AI providers, but the inspected source does not resolve the setup's effects or consent behavior. This supports a warning, not a finding of malicious behavior.
Evidence
dist/upgrade/packages.jsdist/upgrade/package-project.js
Decision evidence
public snapshotAI called this Suspicious at 78.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- During package upgrades, detected AI providers are passed to a setup command with a force flag.
- The provider detector includes Codex by default and detects other providers from project files.
- The inspected API dependency sends requests to the URL supplied to its fetcher.
- The action-types generator builds route type content from collected routes.
Evidence against
- The provider setup is invoked by the package upgrade flow; the inspected source does not establish an npm install hook or show the setup command's configuration effects.
- The inspected fetcher excerpt shows a generic request operation, not collection or forwarding of saved credentials.
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/upgrade/framework.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.255.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.255 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.