This report does not block or authorize the manifest or ZIP.
Static analysis flagged many command, network, filesystem, environment, and heuristic patterns, but most are false positives caused by Markdown fences, official Prisma documentation links, and illustrative code samples. The confirmed concern is operational: the skill recommends Prisma migration, reset, resolve, and database inspection commands that can change databases if executed without explicit user review.
Report position
Historical report
Open audit history before using this report to install.
Audit attestation
Not attestable
The required immutable binding is incomplete.
Human verification
Not verified
No human verification is recorded for this report.
Coverage
1 Files scanned · 356 Lines analyzed
4 items shown for review
Limitations
This report does not claim runtime or sandbox execution and does not prove the absence of side effects.
01
Evidence chain
Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.
The skill recommends Prisma migration commands, including development resets and production deploy or resolve actions. These are legitimate Prisma operations, but they can modify schema state or destroy development data if run automatically or against the wrong database.
The referenced lines explicitly discuss migration reset, deploy, resolve, production testing, and rollback planning. The risk is operational misuse rather than malicious intent.
The skill includes a psql command for checking active PostgreSQL connections. This is useful diagnostics, but it can access a real database depending on the active environment and credentials.
The command is concrete and database-facing, but it performs a read-only count query and does not show credential collection or exfiltration.
The hardcoded URLs point to Prisma documentation pages. I did not find evidence of data exfiltration endpoints, tracking webhooks, or commands that send local data to those URLs.
The listed URLs all use the prisma.io documentation domain. The surrounding text presents them as reference resources only.
The skill shows NODE_ENV usage and an example DATABASE_URL with placeholder credentials. It does not instruct the agent to read a .env file or expose connection strings, but database URL examples should still be treated carefully.
The environment variable references appear in TypeScript and env examples for connection management. No evidence found of secret harvesting or network transmission.
03
Risk findings
Confirmed security concerns are separated from items that still need review.
No confirmed security findings were recorded for this completed audit.
04
Expert evidence
Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.
Artifact subject
Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable
Analysis metadata
Audit model: codex
Analysis state: Complete
Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.
Static analysis classified many backticks and fenced examples as Ruby or shell execution. The file is Markdown guidance, not executable Ruby code, so these locations are false positives except where they document commands a user may choose to run.
The evidence is inside Markdown code fences in SKILL.md. No executable script file, dynamic evaluation, or command injection path is present.
Weak Cryptography and Reconnaissance Alerts Are False Positives
Static analysis reported weak cryptography and reconnaissance patterns, but the inspected context is Prisma schema, relation, migration, query, and checklist guidance. I did not find cryptographic operations, malicious reconnaissance, or prompt injection text.
The scanner appears to match common substrings in domain-specific prose. Manual review found no code implementing weak hashes, scanning networks, or overriding evaluator instructions.