registry / @stacksjs/actions / 0.75.309
@stacksjs/actions@0.75.309
The Stacks actions.
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection mapped the flagged network and file behavior to a generic caller-directed HTTP helper and project tooling. The package has no install hook, and no concrete malicious behavior was established.
Static reason
One or more suspicious static signals were detected.
Trigger
The package build runs for its prepublish hook; HTTP requests and route generation occur through invoked APIs.
Impact
No unconsented credential transfer, destructive action, or hidden payload execution was established.
Mechanism
The HTTP helper uses a caller-provided URL and token, and the inspected package contains no caller that forwards saved credentials through it.
AI rationale
Source inspection mapped the flagged network and file behavior to a generic caller-directed HTTP helper and project tooling. The package has no install hook, and no concrete malicious behavior was established.
Decision evidence
public snapshotAI called this Clean at 84.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the package entrypoints and defines only a build command for its prepublish hook.
- Importing the main entrypoint registers the action runner; named actions are routed through the package API.
- The HTTP helper accepts a token from its caller and sends requests to the URL passed to its request method; no package call site using that token helper was found.
- Route generation loads the project route registry and produces generated route-name data when invoked.
- The inspected dependency entrypoints delegate named action execution or export ordinary API and authentication modules; their manifests show build or typecheck scripts.
- Package discovery reads project package metadata, while the lock checker compares workspace declarations with lock data.
Evidence against
- Static flags identify network, environment, and dynamic-loading patterns, but the inspected source did not establish package-selected credential forwarding or another concrete attack.
Behavioral surface
ChildProcessCrypto
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.309.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.309 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.