Skip to content
skillsafebeta
← Report library
Purpose / Data analysis

Prisma Postgres Skill Security Audit

What the author says it does (original text)

Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, and Management API SDK. Use when creating Prisma Postgres databases, working in Prisma Console, provisioning with create-db/create-pg/create-postgres, or integrating programmatic provisioning with service tokens or OAuth.

Independent security check

Do not install or run it yet

Files checked
5
Risks found
5
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.Risks found: 1
High risk

Unpinned npm/npx commands execute code fetched at installation time

Source references: 6
What we found

The guidance repeatedly uses `@latest` and installs packages without fixed versions. The code executed is therefore determined by the current npm release rather than a version auditable in this Skill.

Why this matters

If a package, publisher account, or dependency chain is compromised, installation or CLI code could read files, environment variables, and credentials or modify the workspace with the user's permissions.

The guide provides several executable `npx` commands using `@latest` plus an SDK install with no version. Consequently, the downloaded and executed code depends on npm's state at runtime. This is a supply-chain and reproducibility risk, not evidence that any package is malicious. Users can request pinned, verified versions for each package.

SKILL.md:56In the instructionsOpen original file
```bashnpx create-db@latest```
Show 5 other places
SKILL.md:75In the instructionsOpen original file
```bashnpx -y @prisma/cli@latest database create --helpnpx -y @prisma/cli@latest database list --json
SKILL.md:125In the instructionsOpen original file
```bashnpm install @prisma/management-api-sdk```
references/create-db-cli.md:69In the instructionsOpen original file
```bashnpm install create-db# orbun add create-db```
SKILL.md:55In the instructionsOpen original file
```bashnpx create-db@latest```Aliases:```bashnpx create-pg@latestnpx create-postgres@latest```
SKILL.md:122In the instructionsOpen original file
Install and use:```bashnpm install @prisma/management-api-sdk```
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.Risks found: 2
Medium risk

Database credentials and claim URLs can be written, copied, or printed

Source references: 3
What we found

The Skill supports writing `DATABASE_URL` and `CLAIM_URL` to `.env`, copying a connection string to the clipboard, printing only that string, and logging connection and claim URLs in sample code.

Why this matters

Terminal logs, CI output, clipboard history, screen sharing, or other processes able to read `.env` could obtain database access. A claim URL may also let another party claim the temporary database.

These are explicit output options and examples: credentials and the claim URL can be written to a chosen `.env`, copied to the system clipboard, printed to the terminal, or logged by sample code. If logs, terminal output, clipboard contents, or the target file are accessible to others, database credentials or the claim link may be exposed. Users can avoid these options, restrict `.env` access, and request redacted examples.

references/create-db-cli.md:50In the instructionsOpen original file
| `--json [boolean]` | `-j` | Output machine-readable JSON || `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` || `--ttl [string]` | `-t` | Auto-delete after a TTL like `30m` or `1h-24h` || `--copy [boolean]` | `-c` | Copy the connection string to the clipboard || `--quiet [boolean]` | `-q` | Only print the connection string || `--open [boolean]` | `-o` | Open the claim URL in your browser |
Show 2 other places
references/create-db-cli.md:84In the instructionsOpen original file
if (isDatabaseSuccess(result)) {  console.log(result.connectionString);  console.log(result.claimUrl);  console.log(result.deletionDate);}
references/create-db-cli.md:49In the instructionsOpen original file
| `--interactive [boolean]` | `-i` | Open region selector || `--json [boolean]` | `-j` | Output machine-readable JSON || `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` || `--ttl [string]` | `-t` | Auto-delete after a TTL like `30m` or `1h-24h` || `--copy [boolean]` | `-c` | Copy the connection string to the clipboard || `--quiet [boolean]` | `-q` | Only print the connection string || `--open [boolean]` | `-o` | Open the claim URL in your browser |
Medium risk

Console edits and schema migration may modify the wrong database

Source references: 2
What we found

The guidance permits editing data in Studio and suggests `prisma migrate dev` after linking, but does not require confirming the selected workspace, project, branch, or whether it is production.

Why this matters

If the wrong project is selected or `.env` points to another database, user data or database structure could be changed unintentionally, causing data loss, application failures, or downtime.

The workflow does require selecting a workspace and project, but then permits editing data in Studio without a separate branch or production-environment confirmation; after linking, it also suggests `prisma migrate dev` when schema application is needed. Thus, selecting the wrong project, connection, or environment could modify the wrong database. This is not hidden behavior, but users can require the database ID, branch, host, and environment to be shown before edits or migrations and prohibit production writes.

references/console-and-connections.md:15In the instructionsOpen original file
1. Open `https://console.prisma.io`.2. Select workspace and project.3. Use dashboard metrics for usage and billing visibility.4. Open the **Studio** tab in the sidebar to inspect and edit data.
Show 1 other places
references/console-and-connections.md:42In the instructionsOpen original file
This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `--force` to re-link. After linking, run `prisma generate`, then `prisma migrate dev` if you need to apply the schema.
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.Risks found: 1
Medium risk

Project linking makes a persistent local `.env` change

Source references: 3
What we found

The guidance says linking creates or updates `.env` and permits re-linking with `--force`, but does not require showing the target file, preserving the old value, or confirming the current project first.

Why this matters

An existing `DATABASE_URL` could be replaced, causing the application, tests, or later migrations to target a different database. The file might also be accidentally committed or included in build artifacts.

The guide explicitly says linking creates or updates the local `.env`, and permits `--force` when already linked. This is intended behavior, but running it in the wrong directory, against the wrong database, or in a project with existing configuration could replace `DATABASE_URL` and redirect later application or migration activity. No preview or backup step is shown; users can require the target path and diff to be shown first and restrict automatic use of `--force`.

references/console-and-connections.md:30In the instructionsOpen original file
If the Prisma Postgres database already exists, link the local project instead of provisioning a new one:```bashprisma postgres link```For CI or non-interactive usage:```bashprisma postgres link --api-key "<your-api-key>" --database "db_..."```This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `--force` to re-link. After linking, run `prisma generate`, then `prisma migrate dev` if you need to apply the schema.
Show 2 other places
references/console-and-connections.md:28In the instructionsOpen original file
## Linking an existing projectIf the Prisma Postgres database already exists, link the local project instead of provisioning a new one:```bashprisma postgres link```
references/console-and-connections.md:42In the instructionsOpen original file
This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `--force` to re-link. After linking, run `prisma generate`, then `prisma migrate dev` if you need to apply the schema.
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.Risks found: 1
Low risk

The install command does not pin a dependency version

Source references: 7
What we found

The installation command does not specify dependency versions. The same command may download different code later, so what you install can differ from what was checked.

Why this matters

A later install may download different code even though the command and this report have not changed.

This is an actionable `npx` command, and `@latest` selects whatever version is current at execution time rather than a fixed, reviewable release. If an upstream release changes or is compromised, the command may execute different code. Users can ask for a tested exact version and verify the package name, version, and source before running it.

This alias also uses `@latest`, so it downloads and executes the release available at that time. Although its stated purpose is database creation, the result is not reproducible, and the alias package should independently be verified as Prisma-controlled. Users can request a pinned version and check the npm publisher.

This alias uses `@latest`, making the executed content depend on npm's current release at runtime. It is an actionable command, not merely a warning; an upstream change could cause users to execute code not reviewed in this Skill. Users can request a pinned version and verify ownership of the alias package.

The install command does not specify an SDK version, so executions at different times may install different implementations. The package is subsequently used with service tokens, OAuth, and token refresh, making version drift relevant to credential handling. Users can request a tested exact version and lockfile and restrict token privileges.

SKILL.md:56In the instructionsOpen original file
```bashnpx create-db@latest```
Show 6 other places
SKILL.md:53In the instructionsOpen original file
Use `create-db` when you need a database immediately:```bashnpx create-db@latest```
SKILL.md:62In the instructionsOpen original file
```bashnpx create-pg@latestnpx create-postgres@latest
SKILL.md:59In the instructionsOpen original file
Aliases:```bashnpx create-pg@latestnpx create-postgres@latest```
SKILL.md:63In the instructionsOpen original file
npx create-pg@latestnpx create-postgres@latest```
SKILL.md:125In the instructionsOpen original file
```bashnpm install @prisma/management-api-sdk```
SKILL.md:120In the instructionsOpen original file
### 5. Type-safe integration with Management API SDKInstall and use:```bashnpm install @prisma/management-api-sdk```Use `createManagementApiClient` for existing tokens, or `createManagementApiSdk` for OAuth + token refresh.
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

6 instruction sections

This Skill is operational guidance for Prisma Postgres covering Console use, temporary and persistent database creation, local-project linking, and the Management API/SDK; it contains no automatically executed script.

View source
SKILL.md:12In the instructionsOpen original file
Guidance for creating, managing, and integrating Prisma Postgres across interactive and programmatic workflows.
SKILL.md:16In the instructionsOpen original file
Reference this skill when:- Setting up Prisma Postgres from Prisma Console- Provisioning instant temporary databases with `create-db`- Linking an existing local project with `prisma postgres link`- Managing Prisma Postgres resources via Management API- Using `@prisma/management-api-sdk` in TypeScript/JavaScript- Handling claim URLs, connection strings, regions, and auth flows

Databases created with `create-db` are temporary by default and are deleted after about 24 hours; the claim URL printed by the command can make one persistent.

View source
references/create-db-cli.md:58In the instructionsOpen original file
- Databases are temporary by default.- Unclaimed databases are auto-deleted after ~24 hours.- Claim the database using the URL shown in command output to keep it permanently.

The linking command creates or updates `DATABASE_URL` in the local `.env`; a subsequent migration command can apply the local schema to the connected database.

View source
references/console-and-connections.md:42In the instructionsOpen original file
This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `--force` to re-link. After linking, run `prisma generate`, then `prisma migrate dev` if you need to apply the schema.

The Management API can create, list, and revoke workspace service tokens. The guidance states that new tokens and connection credentials are shown only once and warns against logging full responses.

View source
references/management-api-sdk.md:34In the instructionsOpen original file
The typed client exposes routes to list, create, and revoke workspace service tokens:- `GET /v1/workspaces/{workspaceId}/service-tokens`- `POST /v1/workspaces/{workspaceId}/service-tokens`- `DELETE /v1/workspaces/{workspaceId}/service-tokens/{serviceTokenId}`Creation accepts a display `name`. The response's `data.value` is the complete token and is returned exactly once; transfer it directly to the intended secret store without logging the response. Later list calls return metadata and `valueHint`, not the token value. Treat revocation as destructive and resolve both ids explicitly.
references/management-api.md:64In the instructionsOpen original file
Connection create/rotate responses reveal credentials once. Later reads redact or omit the secret, so store the URL immediately. Use the structured direct/pooled endpoint returned by the concrete operation; do not assume a historical flat response shape.Workspace service-token creation also returns the complete token value exactly once. List calls expose only metadata and a `valueHint`; delete revokes the token. Keep workspace and token ids opaque, and never log a create response.
Start here · InstructionsSKILL.md
prisma-postgres
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.

File reference map

References: 4
Files making referencesReferenced content
Lines show actual file references, not execution order. Select a node to highlight its connections and inspect the files and source locations. Dashed lines include files that still need locating.
Files and check records5 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included
  • references/console-and-connections.mdFull text included
  • references/create-db-cli.mdFull text included
  • references/management-api-sdk.mdFull text included
  • references/management-api.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions
  • references/console-and-connections.mdSupporting file
  • references/create-db-cli.mdSupporting file
  • references/management-api-sdk.mdSupporting file
  • references/management-api.mdSupporting file

Operations mentioned in code and instructions

Connect to websites
SKILL.md:46In the instructionsOpen original file
- Open `https://console.prisma.io`- Create/select workspace and project
SKILL.md:107In the instructionsOpen original file
```texthttps://api.prisma.io/v1```
SKILL.md:112In the instructionsOpen original file
- OpenAPI docs: `https://api.prisma.io/v1/doc`- Swagger Editor: `https://api.prisma.io/v1/swagger-editor`
Run commands
SKILL.md:55In the instructionsOpen original file
```bashnpx create-db@latest
SKILL.md:61In the instructionsOpen original file
```bashnpx create-pg@latest
SKILL.md:74In the instructionsOpen original file
```bashnpx -y @prisma/cli@latest database create --help
Install extra software packages
SKILL.md:56In the instructionsOpen original file
```bashnpx create-db@latest```
SKILL.md:62In the instructionsOpen original file
```bashnpx create-pg@latestnpx create-postgres@latest
SKILL.md:63In the instructionsOpen original file
npx create-pg@latestnpx create-postgres@latest```
Read keys or account settings
SKILL.md:97In the instructionsOpen original file
```bashprisma postgres link --api-key "<your-api-key>" --database "db_..."```
SKILL.md:100In the instructionsOpen original file
This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `prisma migrate dev`.
references/console-and-connections.md:39In the instructionsOpen original file
```bashprisma postgres link --api-key "<your-api-key>" --database "db_..."```
Lines read
504
File checksum (to compare versions)
cef646596505289420a619faa71c7f23bdf54b66f8f185f08244793af1d8cd0d