Audit History

Environment file access

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

npx create-db@latest --env .env

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Medium

SKILL.md:92-96 references/console-and-connections.md:36-40

Unpinned remote package execution

Several setup commands use npx with the latest tag. A future package release can change what is executed, so users cannot reproduce or review the exact package version first.

The cited commands explicitly use @latest. This is a real supply-chain and reproducibility concern, although the packages are named Prisma tooling.

Medium

API key exposed in command arguments

The non-interactive linking example places an API key directly in a command-line argument. Shell history and process inspection can expose that value.

Both locations show the API key in a CLI argument. Command arguments are commonly recorded by shell history and can be visible to local processes.

Capability review items (3)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

Database connection strings

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Database connection strings

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

references/console-and-connections.md:42 references/console-and-connections.md:49 references/console-and-connections.md:55 references/create-db-cli.md:50 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api.md:63 SKILL.md:98

Database connection strings

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Risk Factors

🔑 Env variables (10)

🌐 Network access (7)

references/management-api-sdk.md:41 references/management-api.md:43 references/management-api.md:16 SKILL.md:46 SKILL.md:105 SKILL.md:110 SKILL.md:111

⚙️ External commands (38)

Audited by: claude

Audit version 6

Jul 21, 2026, 10:21 AM

The skill is documentation and contains no embedded executable code, prompt injection, or unauthorized network behavior. Seven findings are confirmed because documented workflows write database credentials to .env files; two additional medium-risk practices concern unpinned package execution and API keys in command arguments. All remaining static findings are Markdown or documentation-pattern false positives.

5

Files scanned

476

Lines analyzed

12

Review items

0

False positives ignored

Confirmed security concerns (6)

High

Environment file access

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

npx create-db@latest --env .env

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Medium

SKILL.md:92-96 references/console-and-connections.md:36-40

Unpinned remote package execution

Several setup commands use npx with the latest tag. A future package release can change what is executed, so users cannot reproduce or review the exact package version first.

The cited commands explicitly use @latest. This is a real supply-chain and reproducibility concern, although the packages are named Prisma tooling.

Medium

API key exposed in command arguments

The non-interactive linking example places an API key directly in a command-line argument. Shell history and process inspection can expose that value.

Both locations show the API key in a CLI argument. Command arguments are commonly recorded by shell history and can be visible to local processes.

Capability review items (3)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

Database connection strings

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Database connection strings

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

references/console-and-connections.md:42 references/console-and-connections.md:49 references/console-and-connections.md:55 references/create-db-cli.md:50 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api.md:63 SKILL.md:98

Database connection strings

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Risk Factors

🔑 Env variables (10)

🌐 Network access (7)

references/management-api-sdk.md:41 references/management-api.md:43 references/management-api.md:16 SKILL.md:46 SKILL.md:105 SKILL.md:110 SKILL.md:111

⚙️ External commands (38)

Audited by: claude

Audit version 5

Jul 21, 2026, 10:21 AM

The skill is documentation and contains no embedded executable code, prompt injection, or unauthorized network behavior. Seven findings are confirmed because documented workflows write database credentials to .env files; two additional medium-risk practices concern unpinned package execution and API keys in command arguments. All remaining static findings are Markdown or documentation-pattern false positives.

5

Files scanned

476

Lines analyzed

12

Review items

0

False positives ignored

Confirmed security concerns (6)

High

Environment file access

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

npx create-db@latest --env .env

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Medium

SKILL.md:92-96 references/console-and-connections.md:36-40

Unpinned remote package execution

Several setup commands use npx with the latest tag. A future package release can change what is executed, so users cannot reproduce or review the exact package version first.

The cited commands explicitly use @latest. This is a real supply-chain and reproducibility concern, although the packages are named Prisma tooling.

Medium

API key exposed in command arguments

The non-interactive linking example places an API key directly in a command-line argument. Shell history and process inspection can expose that value.

Both locations show the API key in a CLI argument. Command arguments are commonly recorded by shell history and can be visible to local processes.

Capability review items (3)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

Database connection strings

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Database connection strings

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

references/console-and-connections.md:42 references/console-and-connections.md:49 references/console-and-connections.md:55 references/create-db-cli.md:50 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api.md:63 SKILL.md:98

Database connection strings

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Risk Factors

🔑 Env variables (10)

🌐 Network access (7)

references/management-api-sdk.md:41 references/management-api.md:43 references/management-api.md:16 SKILL.md:46 SKILL.md:105 SKILL.md:110 SKILL.md:111

⚙️ External commands (38)

Audited by: claude

Audit version 4

Jul 21, 2026, 10:21 AM

The skill is documentation and contains no embedded executable code, prompt injection, or unauthorized network behavior. Seven findings are confirmed because documented workflows write database credentials to .env files; two additional medium-risk practices concern unpinned package execution and API keys in command arguments. All remaining static findings are Markdown or documentation-pattern false positives.

5

Files scanned

476

Lines analyzed

12

Review items

0

False positives ignored

Confirmed security concerns (6)

High

Environment file access

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

npx create-db@latest --env .env

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Medium

SKILL.md:92-96 references/console-and-connections.md:36-40

Unpinned remote package execution

Several setup commands use npx with the latest tag. A future package release can change what is executed, so users cannot reproduce or review the exact package version first.

The cited commands explicitly use @latest. This is a real supply-chain and reproducibility concern, although the packages are named Prisma tooling.

Medium

API key exposed in command arguments

The non-interactive linking example places an API key directly in a command-line argument. Shell history and process inspection can expose that value.

Both locations show the API key in a CLI argument. Command arguments are commonly recorded by shell history and can be visible to local processes.

Capability review items (3)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

Database connection strings

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Database connection strings

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

references/console-and-connections.md:42 references/console-and-connections.md:49 references/console-and-connections.md:55 references/create-db-cli.md:50 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api.md:63 SKILL.md:98

Database connection strings

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Risk Factors

🔑 Env variables (10)

🌐 Network access (7)

references/management-api-sdk.md:41 references/management-api.md:43 references/management-api.md:16 SKILL.md:46 SKILL.md:105 SKILL.md:110 SKILL.md:111

⚙️ External commands (38)

Audited by: claude

Audit version 3

Jul 21, 2026, 10:21 AM

The skill is documentation and contains no embedded executable code, prompt injection, or unauthorized network behavior. Seven findings are confirmed because documented workflows write database credentials to .env files; two additional medium-risk practices concern unpinned package execution and API keys in command arguments. All remaining static findings are Markdown or documentation-pattern false positives.

5

Files scanned

476

Lines analyzed

12

Review items

0

False positives ignored

Confirmed security concerns (6)

High

Environment file access

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

npx create-db@latest --env .env

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Medium

SKILL.md:92-96 references/console-and-connections.md:36-40

Unpinned remote package execution

Several setup commands use npx with the latest tag. A future package release can change what is executed, so users cannot reproduce or review the exact package version first.

The cited commands explicitly use @latest. This is a real supply-chain and reproducibility concern, although the packages are named Prisma tooling.

Medium

API key exposed in command arguments

The non-interactive linking example places an API key directly in a command-line argument. Shell history and process inspection can expose that value.

Both locations show the API key in a CLI argument. Command arguments are commonly recorded by shell history and can be visible to local processes.

Capability review items (3)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

Database connection strings

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Database connection strings

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

references/console-and-connections.md:42 references/console-and-connections.md:49 references/console-and-connections.md:55 references/create-db-cli.md:50 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api.md:63 SKILL.md:98

Database connection strings

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Risk Factors

🔑 Env variables (10)

🌐 Network access (7)

references/management-api-sdk.md:41 references/management-api.md:43 references/management-api.md:16 SKILL.md:46 SKILL.md:105 SKILL.md:110 SKILL.md:111

⚙️ External commands (38)

Audited by: claude

Audit version 2

Jul 21, 2026, 10:21 AM

The skill is documentation and contains no embedded executable code, prompt injection, or unauthorized network behavior. Seven findings are confirmed because documented workflows write database credentials to .env files; two additional medium-risk practices concern unpinned package execution and API keys in command arguments. All remaining static findings are Markdown or documentation-pattern false positives.

5

Files scanned

476

Lines analyzed

12

Review items

0

False positives ignored

Confirmed security concerns (6)

High

Environment file access

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

npx create-db@latest --env .env

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Medium

SKILL.md:92-96 references/console-and-connections.md:36-40

Unpinned remote package execution

Several setup commands use npx with the latest tag. A future package release can change what is executed, so users cannot reproduce or review the exact package version first.

The cited commands explicitly use @latest. This is a real supply-chain and reproducibility concern, although the packages are named Prisma tooling.

Medium

API key exposed in command arguments

The non-interactive linking example places an API key directly in a command-line argument. Shell history and process inspection can expose that value.

Both locations show the API key in a CLI argument. Command arguments are commonly recorded by shell history and can be visible to local processes.

Capability review items (3)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

Database connection strings

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Database connection strings

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

references/console-and-connections.md:42 references/console-and-connections.md:49 references/console-and-connections.md:55 references/create-db-cli.md:50 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api-sdk.md:24 references/management-api-sdk.md:40 references/management-api.md:63 SKILL.md:98

Database connection strings

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Risk Factors

🔑 Env variables (10)

🌐 Network access (7)

references/management-api-sdk.md:41 references/management-api.md:43 references/management-api.md:16 SKILL.md:46 SKILL.md:105 SKILL.md:110 SKILL.md:111

⚙️ External commands (38)

Audited by: claude

Audit version 1

Jul 21, 2026, 10:21 AM

The skill is documentation and contains no embedded executable code, prompt injection, or unauthorized network behavior. Seven findings are confirmed because documented workflows write database credentials to .env files; two additional medium-risk practices concern unpinned package execution and API keys in command arguments. All remaining static findings are Markdown or documentation-pattern false positives.

5

Files scanned

476

Lines analyzed

12

Review items

0

False positives ignored

Confirmed security concerns (6)

High

Environment file access

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

npx create-db@latest --env .env

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Environment file access

This flow updates your local `.env` with `DATABASE_URL`, then you can run `prisma generate` and `pri

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

Medium

SKILL.md:92-96 references/console-and-connections.md:36-40

Unpinned remote package execution

Several setup commands use npx with the latest tag. A future package release can change what is executed, so users cannot reproduce or review the exact package version first.

The cited commands explicitly use @latest. This is a real supply-chain and reproducibility concern, although the packages are named Prisma tooling.

Medium

API key exposed in command arguments

The non-interactive linking example places an API key directly in a command-line argument. Shell history and process inspection can expose that value.

Both locations show the API key in a CLI argument. Command arguments are commonly recorded by shell history and can be visible to local processes.

Capability review items (3)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

Database connection strings

This command updates or creates `.env` with `DATABASE_URL`. If the project is already linked, use `-

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High

Database connection strings

| `--env [string]` | `-e` | Write `DATABASE_URL` and `CLAIM_URL` into a target `.env` |

The documented command writes a database credential to a local .env file when executed. This is a legitimate workflow, but it changes a sensitive file and requires explicit user approval and secret handling.

High