📦

Audit History

prisma-driver-adapter-implementation - 8 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v8 LatestJul 23, 2026, 05:44 PM 1 confirmed0No capability change
v7 Jul 21, 2026, 10:22 AM No confirmed findings0No capability change
v6 Jul 21, 2026, 10:22 AM No confirmed findings0No capability change
v5 Jul 21, 2026, 10:22 AM No confirmed findings0No capability change
v4 Jul 21, 2026, 10:22 AM No confirmed findings0No capability change
v3 Jul 21, 2026, 10:22 AM No confirmed findings0No capability change
v2 Jul 21, 2026, 10:22 AM No confirmed findings0No capability change
v1 Jul 21, 2026, 10:22 AM No confirmed findings0Baseline

Jul 23, 2026, 05:44 PM

All 69 static alerts are false positives from Markdown, TypeScript examples, expected byte decoding, and a standard DATABASE_URL reference. A separate high-severity data-integrity issue exists because connectToShadowDb() can reuse the primary database URL.

1
Files scanned
639
Lines analyzed
3
Review items
0
False positives ignored

Confirmed security concerns (1)

High
Primary Database Reused as Shadow Database
connectToShadowDb() falls back to the primary connection URL when no shadow URL is supplied. Migration shadow operations could alter or erase primary data.
The fallback is explicit in the example, and shadow databases are isolated migration workspaces. Reusing the primary URL creates a direct data-integrity hazard.
Audited by: codex