registry / @stacksjs/actions / 0.75.339
@stacksjs/actions@0.75.339
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged AWS credential access is within deployment code, and the GitHub token flow is used for an explicit release operation against GitHub. The package declares no install-time hook, and the inspected import path does not perform those operations automatically.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Importing the main entry registers the action runner; deployment, release publication, and development servers are exposed as callable operations.
Impact
No unsolicited credential transfer, install-time contact, hidden account action, or unrelated destructive behavior was found in the inspected paths.
Mechanism
The reviewed credential handling and network operations are associated with deployment or publishing workflows and target the corresponding cloud or GitHub services.
AI rationale
The flagged AWS credential access is within deployment code, and the GitHub token flow is used for an explicit release operation against GitHub. The package declares no install-time hook, and the inspected import path does not perform those operations automatically.
Network endpoints1
api.github.com
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The registry entry point initializes the action runner and exports package APIs; the inspected code shows no top-level credential collection or network request there.
- The only declared lifecycle hook is prepublishOnly, which runs the build; no install-time hook is declared.
- AWS credential loading appears in the deployment action, where project environment files supply credentials for deployment.
- GitHub release publication is an exported operation that uses the repository's GitHub API and can skip when the project origin is not a GitHub repository.
Evidence against
- The package includes deployment and development-server capabilities that can read project files, access the network, and start processes when invoked.
- The package's main entry point exports many modules, so the broad API surface merits review; the inspected entry and flagged paths did not reveal automatic malicious behavior.
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/dev/system-tray.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.339.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.339 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.