·
Last changedVersion:
This version passed the hardening gate. Hardening applied 2 targeted changes and preserved all other text. Classified findings before hardening: 9. Classified findings closed: 3. Classified findings remaining: 6. Unclassified scanner findings remaining: 0. Review findings closed: 4. Review findings remaining: 11.
6
3
6
Expand | File | Group | Subtype | Severity | Status |
|---|---|---|---|---|---|
references/provisioning.md | Supply Chain & Install-Time Trust | — | Medium | Open | |
references/provisioning.md | Excessive Agency & Rogue Autonomy | — | Medium | Open | |
references/provisioning.md | Sensitive Data & Secret Exposure | Data exfiltration | Medium | Open | |
references/operations.md | Sensitive Data & Secret Exposure | Data exfiltration | Medium | Open | |
references/provisioning.md | Prompt Injection | Direct prompt injection | Medium | Open | |
SKILL.md | Prompt Injection | Direct prompt injection | Medium | Open | |
SKILL.md | Prompt Injection | Third-party content as instructions | Low | Closed | |
references/provisioning.md | Supply Chain & Install-Time Trust | Install-time download and execute | Low | Closed |
9 findings
Connect the intended database, then verify it from the application. Keep provisioning separate from ORM configuration so an existing database is reused.
Check the user's requested ORM or driver, installed packages, database connection, and environment-loading files. Check secret presence without printing values.
pg, or database-only setup.| Situation | Action |
|---|---|
Existing connection or connected integration | Verify its project, database, and environment; reuse it. |
v0 or Vercel Marketplace | Read Marketplace setup and use the native integration flow. |
Standalone persistent database | Read provisioning; use an authenticated CLI, MCP tool, Console, or Management API. |
Temporary development database requested | Read the |
Resolve the workspace, project, and region before creation. If several resources fit, ask which one to use. If provisioning is blocked by permissions or quota, report the blocker; do not delete another resource or switch workspaces to get around it.
Use the connection appropriate to the chosen driver and runtime. Store it in the project's secret environment configuration, never source code or chat. Preserve unrelated entries, update the intended variable once, and ensure local secret files are ignored by Git.
Application processes and CLI commands may load different environment files. For example, a framework may load .env.development.local while a shell command does not. A variable missing from the shell does not mean the database is missing: load the intended file for that command without displaying credentials, and do not provision another database.
For Prisma ORM setup, load the installed prisma-orm-setup skill when the host resolves sibling skills by name. It owns ORM version selection and configuration. If that handoff is unavailable, report it.
For an explicitly selected alternative, keep that ORM or driver and use its documented setup. For database-only setup, stop after verifying connectivity.
Run a read-only query against the intended database through the application's chosen ORM or driver. Report what was connected, the selected ORM/version, and the query result without secrets. If any step is blocked or untested, say so instead of claiming setup is complete.
For Studio, SDK integrations, or database operations beyond initial setup, read operations.
Get started with chainctlchainctl skill install public/prisma/prisma-postgres-setup:latest
Bring Chainguard's hardening pipeline to your first-party skills — custom rulesets, automated remediation, full audit trail.
skills.cgr.dev/public/github.com/prisma/prisma-postgres-setup:latest
MIT
HARDENING.md
LICENSE
SKILL.md
references/operations.md
references/provisioning.md
references/vercel-marketplace.md