registry / @stacksjs/actions / 0.75.281
@stacksjs/actions@0.75.281
The Stacks actions.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime and flagged source paths implement project-aligned library functions. Scanner signals around dynamic loading, networking, credentials, and process execution resolve to consumer-configured linting, caller-directed API requests, GitHub release operations, and explicitly selected project scripts.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
These functions run when a consumer imports or explicitly calls the corresponding package API.
Impact
No malicious impact was established from the inspected source.
Mechanism
The inspected code processes caller or project data and uses ordinary library operations; it shows no automatic credential collection, unrelated credential transfer, or install-time mutation.
AI rationale
The manifest has no install lifecycle hook, and the inspected runtime and flagged source paths implement project-aligned library functions. Scanner signals around dynamic loading, networking, credentials, and process execution resolve to consumer-configured linting, caller-directed API requests, GitHub release operations, and explicitly selected project scripts.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines only a prepublishOnly build hook; it has no install-time hook.
- The inspected dependency entrypoints expose action-running, API-client, and authentication libraries; their manifests show build and typecheck scripts rather than install hooks.
- The API helper sends the supplied URL, headers, and body through fetch; it does not add a package-selected credential recipient.
- The runtime hint is a route-type generator that gathers registered routes and writes generated route types.
- The flagged project tools inspect package metadata, validate lockfile consistency, and run only named scripts declared by the consumer, checking that the project manifest remains unchanged.
- The GitHub release helper obtains GitHub credentials for release requests to the GitHub API; the lint helper loads the project’s own lint configuration.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystem
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.281.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.281 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.