registry / @stacksjs/actions / 0.75.276
@stacksjs/actions@0.75.276
⚠ Under reviewThe Stacks actions.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe inspected lifecycle and flagged source paths show build-time publishing and ordinary framework operations, with no verified attack. Several selected registry dependencies remain unresolved in this bounded inspection, so the package cannot be cleared.
Static reason
One or more suspicious static signals were detected.
Trigger
Importing and using the package’s runtime API.
Impact
The unresolved dependency behavior prevents clearing the package’s full runtime supply chain.
Mechanism
The package entry point loads registry dependencies and reexports runtime features; source for several selected dependencies was outside the inspected snapshot.
AI rationale
The inspected lifecycle and flagged source paths show build-time publishing and ordinary framework operations, with no verified attack. Several selected registry dependencies remain unresolved in this bounded inspection, so the package cannot be cleared.
Evidence
package.jsondist/index.js
Decision evidence
public snapshotAI called this Manual Review at 72.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest’s only lifecycle hook is prepublishOnly, which runs the build.
- The runtime entry point imports the action runner and reexports a broad API; the manifest declares many registry dependencies.
- Package discovery writes a generated package manifest, and the pantry-lock code checks declared dependency versions.
- Several selected runtime dependency sources are unavailable in this bounded snapshot, so their behavior remains unresolved.
Evidence against
- The inspected high-signal files show package discovery, lockfile validation, and route type generation; no concrete attack behavior was identified in them.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
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.276.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.276 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.