8import fsPromises__default, { readFile, mkdir, writeFile, chmod } from 'node:fs/promises';
L9: import require$$0, { execFileSync, ChildProcess, execFile, spawnSync, spawn } from 'node:child_process';
L10: import { createServer } from 'node:http';
L11: import require$$4, { styleText, debuglog, stripVTControlCharacters, inspect, promisify, callbackify, aborted as aborted$1 } from 'node:util';
L12: import process$3, { stdout, stdin, platform, hrtime, execPath, execArgv } from 'node:process';
L13: import * as l from 'node:readline';
...
L88: // with no body, we should not to set Content-Type
L89: serializedBody === void 0 || // if serialized body is FormData; browser will correctly set Content-Type & boundary expression
L90: serializedBody instanceof FormData ? {} : {
...
L216: if (parseAs
CriticalHardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/index.jsView on unpkg · L8 8Trigger-reachable chain: manifest.main -> dist/index.js
L8: import fsPromises__default, { readFile, mkdir, writeFile, chmod } from 'node:fs/promises';
L9: import require$$0, { execFileSync, ChildProcess, execFile, spawnSync, spawn } from 'node:child_process';
L10: import { createServer } from 'node:http';
L11: import require$$4, { styleText, debuglog, stripVTControlCharacters, inspect, promisify, callbackify, aborted as aborted$1 } from 'node:util';
L12: import process$3, { stdout, stdin, platform, hrtime, execPath, execArgv } from 'node:process';
L13: import * as l from 'node:readline';
...
L88: // with no body, we should not to set Content-Type
L89: serializedBody === void 0 || // if serialized body is FormData; browser will correctly set Content-Type & boundary expression
L90: serialize
CriticalTrigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L8 8import fsPromises__default, { readFile, mkdir, writeFile, chmod } from 'node:fs/promises';
L9: import require$$0, { execFileSync, ChildProcess, execFile, spawnSync, spawn } from 'node:child_process';
L10: import { createServer } from 'node:http';
HighChild Process
Package source references child process execution.
dist/index.jsView on unpkg · L8 11import require$$4, { styleText, debuglog, stripVTControlCharacters, inspect, promisify, callbackify, aborted as aborted$1 } from 'node:util';
L12: import process$3, { stdout, stdin, platform, hrtime, execPath, execArgv } from 'node:process';
L13: import * as l from 'node:readline';
21235try {
L21236: await execa(packageManager || getPackageManager(), ["install"], {
L21237: cwd: projectPath,
...
L21247: }
L21248: const TEMPLATES_API_URL = process.env.MASTRA_TEMPLATES_API_URL || "https://mastra.ai/api/templates.json";
L21249: async function loadTemplates() {
HighSame File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.jsView on unpkg · L21235 10339// If `subprocess.stdin` is destroyed before being fully written to, it is considered aborted and should throw an error.
L10340: // This can happen for example when user called `subprocess.stdin.destroy()` before `subprocess.stdin.end()`.
L10341: // However, Node.js calls `subprocess.stdin.destroy()` on exit for cleanup purposes.
L10342: // https://github.[redacted]child_process.js#L278
L10343: // This is normal and should not throw an error.
...
L10348: // The only way to detect this is to spy on `subprocess.stdin._destroy()` by wrapping it.
L10349: // If `subprocess.exitCode` or `subprocess.signalCode` is set, it means `.destroy()` is being called by Node.js itself.
L10350: const handleStdinDestroy = (stream, {originalStreams: [originalStdin], subprocess}) => {
HighCommand Output Exfiltration
Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/index.jsView on unpkg · L10339 8import fsPromises__default, { readFile, mkdir, writeFile, chmod } from 'node:fs/promises';
L9: import require$$0, { execFileSync, ChildProcess, execFile, spawnSync, spawn } from 'node:child_process';
L10: import { createServer } from 'node:http';
L11: import require$$4, { styleText, debuglog, stripVTControlCharacters, inspect, promisify, callbackify, aborted as aborted$1 } from 'node:util';
L12: import process$3, { stdout, stdin, platform, hrtime, execPath, execArgv } from 'node:process';
L13: import * as l from 'node:readline';
...
L88: // with no body, we should not to set Content-Type
L89: serializedBody === void 0 || // if serialized body is FormData; browser will correctly set Content-Type & boundary expression
L90: serializedBody instanceof FormData ? {} : {
...
L216: if (parseAs
HighSandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/index.jsView on unpkg · L8 10339Trigger-reachable command-output exfiltration chain: manifest.main -> dist/index.js
L10339: // If `subprocess.stdin` is destroyed before being fully written to, it is considered aborted and should throw an error.
L10340: // This can happen for example when user called `subprocess.stdin.destroy()` before `subprocess.stdin.end()`.
L10341: // However, Node.js calls `subprocess.stdin.destroy()` on exit for cleanup purposes.
L10342: // https://github.[redacted]child_process.js#L278
L10343: // This is normal and should not throw an error.
...
L10348: // The only way to detect this is to spy on `subprocess.stdin._destroy()` by wrapping it.
L10349: // If `subprocess.exitCode` or `subprocess.signalCode` is set, it means `.destroy()` is being called by Node.js itself.
L10350: const handleStdinDestro
HighTrigger Reachable Command Output Exfiltration
A manifest entrypoint or package-local install chain reaches command-output exfiltration behavior.
dist/index.jsView on unpkg · L10339