registry / @stacksjs/actions / 0.75.397
@stacksjs/actions@0.75.397
The Stacks actions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe reported credential lead resolves to AWS credentials used by the package's deployment workflow, and the root import does not trigger that workflow. The package's lifecycle hook only builds the package; the other flagged paths inspected perform ordinary action utilities and repository-scoped release behavior.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Package import wires action utilities; deployment and release actions run through their respective command or function workflows.
Impact
No unrelated credential transmission, unsolicited account action, or harmful automatic behavior was identified.
Mechanism
The deploy workflow reads project AWS configuration for deployment, and release publishing uses a GitHub token for the repository's release API.
AI rationale
The reported credential lead resolves to AWS credentials used by the package's deployment workflow, and the root import does not trigger that workflow. The package's lifecycle hook only builds the package; the other flagged paths inspected perform ordinary action utilities and repository-scoped release behavior.
Network endpoints1
api.github.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package entrypoint is dist/index.js and wires the action runner while exporting action utilities; it does not import the deploy command.
- The only lifecycle script is prepublishOnly, which runs the package build.
- GitHub release publishing obtains a GitHub token only when called and uses it for a release operation on the repository inferred from the user's Git remote.
- The deploy module reads AWS credentials from project environment files as part of its deployment workflow; no unrelated credential collector was identified.
- Package discovery updates a generated package manifest when explicitly called; it does not run as install or root-import behavior.
Evidence against
- Static scanner similarity and semantic-analysis findings are leads, not source evidence of an attack.
- The AWS credential finding points to stacksjs.com, but the inspected match is within email/template content rather than credential transport.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
Source & flagged code
16 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
14 High5 Medium6 Low
HighCopied Package Dependency Bridgedist/discover-packages.js
HighSemantic Analysis Limiteddist/pantry-lock.js
HighKnown Malware Source Similaritydist/setup/ssl.js
HighKnown Malware Source Similaritydist/deploy/index.js
HighKnown Malware Source Similaritydist/dev/system-tray.js
HighKnown Malware Source Similaritydist/project-scripts.js
HighKnown Malware Source Similaritydist/upgrade/framework-utils.js
HighKnown Malware Source Similaritydist/upgrade/framework.js
HighKnown Malware Source Similaritydist/dev/dashboard-supervisor.js
HighKnown Malware Source Similaritydist/make.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to @stacksjs/actions@0.75.397.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.397 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.