技能 prisma-compute
📦
prisma-compute
v1.4.1 内容修订 r2 高风险 🌐 网络访问🔑 环境变量📁 文件系统访问⚙️ 外部命令
安全部署 Prisma Compute 应用
Prisma Compute 部署需要正确的配置、身份验证、环境设置和运行时端口。此技能针对受支持的 TypeScript 框架提供设置、部署、验证和故障排除指导。
支持: Claude Codex Code(CC)
安装前请停下并请求确认。
请审查安装计划，并在更改文件前获得用户明确同意。
使用我的智能体安装
将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。
智能体请求
Review the Skillstore skill "prisma-compute" from https://skillstore.io/skills/prisma-prisma-compute.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-compute/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.你的智能体仍应展示其计划，并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。
测试它
正在使用“prisma-compute”。 部署前检查我的 Next.js 应用。
预期结果:
- 框架：Next.js，需要独立服务器输出。
- 运行时：绑定到部署端口和所有网络接口。
- 下一步：验证生成的部署脚本和配置。
正在使用“prisma-compute”。 我的预览部署无法连接到数据库。
预期结果:
- 检查分支名称是否与分支环境范围匹配。
- 确认部署可以获取非占位符数据库 URL。
- 验证环境配置后使用运行时日志。
正在使用“prisma-compute”。 我有多个 Prisma 工作区。
预期结果:
- 在更改项目或应用状态之前检查当前活动工作区。
- 为非交互式操作选择明确的工作区标识符。
- 不要显示服务令牌或本地凭据文件。
安全审计
高风险v7 • 2026/7/23 打开版本化报告
No prompt injection or malicious collection endpoint was found; most static matches are Markdown or deployment documentation. The skill still handles secret-bearing environment files, executes mutable package versions, and documents non-interactive production mutations.
7
已扫描文件
1,901
分析行数
16
复核项
0
已忽略误报
已确认安全问题 (43)
高
Environment file access
bunx @prisma/cli@latest project env add --file .env --role production
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest project env add --file .env.preview --role preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest project env update --file .env --role production
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
`app deploy --env .env` loads environment variables from a file for the deployment. A config-backed
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
--env .env.preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
显示全部 43 条已确认问题
高
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
--env .env.preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest app deploy api --prod --yes --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
file: [".env", ".env.production"],
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
env: "apps/web/.env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
file: "apps/api/.env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment variant files
file: [".env", ".env.production"],
The configuration explicitly loads .env and .env.production files. These variants commonly contain deployment secrets and therefore require deliberate scope and repository controls.
高
Environment file access
- a `.env` file containing `DATABASE_URL`
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
- an initial Compute deployment with env vars loaded from `.env`
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest app deploy --framework nextjs --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest app deploy --framework nestjs --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest app deploy --framework tanstack-start --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest app deploy --framework nuxt --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest app deploy --framework astro --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
env: "packages/db/.env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
--env packages/db/.env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest project env add --file .env.preview --branch feature/foo
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
test -f .env && sed -n 's/=.*/=<redacted>/p' .env
The command reads a local .env file and prints variable names while redacting values. Redaction reduces exposure, but access to a secret-bearing file is real.
高
Environment file access
bunx @prisma/cli@latest app deploy --json --no-interactive --prod --yes --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
1. Put a real production-ready `DATABASE_URL` in `.env` or project env.
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
4. Redeploy with `--env .env` or project env configured.
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest app deploy --prod --yes --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
bunx @prisma/cli@latest app deploy --branch feature/foo --env .env.preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Environment file access
- `env-deploy-loads-dotenv` - Generated deploy scripts may load env via `prisma.compute.ts` or `--en
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
高
Unpinned Remote Package Execution
Commands repeatedly execute @prisma/cli@latest and create-prisma@latest through package runners. A compromised or unexpectedly changed release would execute with the agent's local privileges.
The cited commands explicitly use the mutable latest tag with bunx. Package runners download and execute that resolved release.
高
Production Mutation Confirmation Bypass
The skill documents production deploy, promotion, rollback, removal, and other remote mutations with non-interactive confirmation flags. Incorrect target inference could alter live infrastructure.
The cited guidance explicitly combines production operations with --yes. Intent guardrails are present, but the commands bypass interactive confirmation once run.
能力复核项 (16)
这些是真实的本地能力，对此技能可能是预期行为，因此需要复核，但不会按已确认恶意行为计分。
高
Database connection strings
bunx @prisma/cli@latest project env add DATABASE_URL=postgresql://... --branch feature/foo
The guidance permits a database URL in command arguments, so substituted credentials can enter shell history or process listings. The example is legitimate but security-sensitive.
高
Database connection strings
bunx @prisma/cli@latest project env update DATABASE_URL=postgresql://... --branch feature/foo
The guidance permits a database URL in command arguments, so substituted credentials can enter shell history or process listings. The example is legitimate but security-sensitive.
高
Database connection strings
- Existing database env values supplied through `--env DATABASE_URL=...`, `--env DIRECT_URL=...`, an
The guidance permits a database URL in command arguments, so substituted credentials can enter shell history or process listings. The example is legitimate but security-sensitive.
高
Database connection strings
- a `.env` file containing `DATABASE_URL`
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
高
Database connection strings
const databaseUrl = process.env.DATABASE_URL
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
高
Database connection strings
if (!databaseUrl) throw new Error("DATABASE_URL is required")
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
高
Database connection strings
envVars: { DATABASE_URL: databaseUrl },
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
高
Database connection strings
1. Put a real production-ready `DATABASE_URL` in `.env` or project env.
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
中
Hidden file access
env: "apps/web/.env",
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
中
Hidden file access
file: "apps/api/.env",
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
中
Hidden file access
env: "packages/db/.env",
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
中
Hidden file access
--env packages/db/.env
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
中
Environment variable access (dot notation)
token: process.env.PRISMA_API_TOKEN,
The SDK example reads PRISMA_API_TOKEN from the process environment and supplies it to an authenticated client. This is legitimate secret access that requires redaction and least privilege.
中
Environment variable access (dot notation)
const databaseUrl = process.env.DATABASE_URL
The SDK example reads DATABASE_URL from the process environment before deployment. This is legitimate credential handling, but accidental logging or broad process access could expose it.
中
Environment variable object
token: process.env.PRISMA_API_TOKEN,
The SDK example reads PRISMA_API_TOKEN from the process environment and supplies it to an authenticated client. This is legitimate secret access that requires redaction and least privilege.
中
Environment variable object
const databaseUrl = process.env.DATABASE_URL
The SDK example reads DATABASE_URL from the process environment before deployment. This is legitimate credential handling, but accidental logging or broad process access could expose it.
风险因素
🌐 网络访问 (6)
🔑 环境变量 (40)
references/app-deploy-cli.md:150 references/app-deploy-cli.md:152 references/app-deploy-cli.md:165 references/app-deploy-cli.md:195 references/compute-config.md:92 references/create-prisma.md:107 references/create-prisma.md:65 references/create-prisma.md:82 references/create-prisma.md:109 references/frameworks.md:127 references/frameworks.md:133 references/frameworks.md:162 references/frameworks.md:169 references/frameworks.md:289 references/frameworks.md:295 references/frameworks.md:127 references/frameworks.md:133 references/frameworks.md:162 references/frameworks.md:169 references/frameworks.md:289 references/frameworks.md:295 references/sdk-api.md:35 references/sdk-api.md:47 references/sdk-api.md:35 references/sdk-api.md:47 references/sdk-api.md:47 references/sdk-api.md:48 references/sdk-api.md:58 references/troubleshooting.md:333 references/troubleshooting.md:333 references/troubleshooting.md:187 references/troubleshooting.md:191 references/troubleshooting.md:197 references/troubleshooting.md:216 references/troubleshooting.md:244 SKILL.md:129 SKILL.md:129 SKILL.md:148 SKILL.md:147 SKILL.md:191
📁 文件系统访问 (5)
⚙️ 外部命令 (50)
SKILL.md:3 SKILL.md:18-23 SKILL.md:23-25 SKILL.md:25 SKILL.md:29-31 SKILL.md:31-34 SKILL.md:34-36 SKILL.md:36 SKILL.md:42 SKILL.md:43 SKILL.md:53-55 SKILL.md:55 SKILL.md:56-59 SKILL.md:59-60 SKILL.md:60-61 SKILL.md:61-62 SKILL.md:62-67 SKILL.md:67-70 SKILL.md:70-73 SKILL.md:73-76 SKILL.md:76-79 SKILL.md:79-82 SKILL.md:82-88 SKILL.md:88-89 SKILL.md:89-90 SKILL.md:90-91 SKILL.md:91-92 SKILL.md:92-93 SKILL.md:93-94 SKILL.md:94-95 SKILL.md:95-101 SKILL.md:101-102 SKILL.md:102 SKILL.md:103 SKILL.md:104-105 SKILL.md:105 SKILL.md:106 SKILL.md:110 SKILL.md:111 SKILL.md:112 SKILL.md:113 SKILL.md:114 SKILL.md:115 SKILL.md:116 SKILL.md:117 SKILL.md:121 SKILL.md:122 SKILL.md:123 SKILL.md:124-128 SKILL.md:128
审计者: codex 查看审计历史 →
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/prisma-prisma-compute/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/prisma-prisma-compute?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/prisma-prisma-compute?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-compute/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/prisma-prisma-compute.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学术引用 (APA · BibTeX · CFF)
APA 引用
prisma. (2026). prisma-compute security audit report (audit version 7) [Author version 1.4.1]. Skillstore. https://skillstore.io/skills/prisma-prisma-compute/audits/7BibTeX 引用
@techreport{prisma-prisma-prisma-compute-2026,
author = {prisma},
title = {prisma-compute security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/prisma-prisma-compute/audits/7},
note = {Author version 1.4.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "prisma-compute security audit report (audit version 7)"
version: "1.4.1"
type: report
authors:
- name: "prisma"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/prisma-prisma-compute/audits/7"
identifiers:
- type: other
value: "skillstore:prisma-prisma-compute:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据 证据置信度: 中 45
架构
100
可维护性
87
内容
65
社区
91
规范符合性
你能构建什么
准备现有服务
检查现有 TypeScript 服务的 Compute 配置、构建输出、环境输入和端口绑定。
部署预览分支
使用明确的项目、应用、分支和预览环境设置来规划分支部署。
解决部署失败问题
使用正确的 CLI 输出和日志，区分身份验证、构建、数据库和运行时故障。
试试这些提示
检查部署就绪情况
检查我的项目是否已准备好部署到 Prisma Compute。检查框架、构建命令、端口绑定和必需配置。
创建 Compute 配置
帮助我为应用创建 prisma.compute.ts 配置。请询问应用根目录、框架、入口点、HTTP 端口和环境文件路径。
规划预览部署
为我的分支规划一次安全的 Prisma Compute 预览部署。在提出命令之前，确定明确的项目、应用、分支和环境设置。
排查部署失败问题
诊断我的 Prisma Compute 部署失败问题。首先将其分类为身份验证、构建、环境、数据库或运行时问题，然后列出侵入性最低的检查步骤。
最佳实践
- 运行部署命令前，检查 CLI 帮助和现有项目配置。
- 为自动化操作使用明确的工作区、项目、应用和分支标识符。
- 将密钥保存在平台或 CI 存储中，绝不输出连接 URL 或令牌。
避免
- 在用户意图不明确且未审查目标的情况下，不要部署到生产环境。
- 不要使用占位符数据库 URL，也不要将密钥值提交到配置文件。
- 不要将本地就绪视为公共部署可访问的证明。
常见问题
此技能会自动部署应用吗？
不会。它提供指导，并且在执行会更改远程应用的命令前应请求确认。
它涵盖哪些框架？
它涵盖已记录的 Next.js、Nuxt、Astro、Hono、NestJS、TanStack Start、自定义应用和 Bun 的 Compute 就绪指导。
我应该提交 prisma.compute.ts 吗？
你可以提交不含密钥的部署默认设置。令牌、连接字符串和密钥值应保存在版本控制之外。
我应该如何处理多个工作区？
检查本地会话，并在进行非交互式更改前选择明确的工作区标识符。
部署会运行数据库迁移吗？
不会。请通过适当的数据库工作流单独运行迁移和种子任务。
失败后我应该检查哪些日志？
构建失败时使用构建日志，运行时部署失败时使用应用日志。
开发者详情
作者
prisma许可证
MIT
作者版本
v1.4.1
Skillstore 修订
r2
引用
ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
维护新鲜度
2026/7/25
使用量
0 次下载 · 0 次浏览
文件结构