This report does not block or authorize the manifest or ZIP.
The verifier script finding is a false positive; it only validates skill metadata. Most SKILL.md findings are Markdown backtick noise, but the skill does direct users to run mutable Alembic commands and includes destructive migration examples. No prompt injection or data exfiltration intent was found, but database safety controls should be strengthened.
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
2 Files scanned · 415 Lines analyzed
15 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.
| `alembic upgrade head` | Apply all pending migrations |
The line instructs use of alembic upgrade head, which applies database schema changes. Running it on the wrong database can cause outages or data loss.
| `alembic upgrade +1` | Apply one migration at a time |
The line instructs use of alembic upgrade +1, which mutates database schema state. It is legitimate but risky without backups and environment confirmation.
| `alembic downgrade -1` | Rollback last migration |
The line instructs use of alembic downgrade -1, which can reverse schema changes and remove data. Downgrades require explicit confirmation and backups.
The fenced bash example applies migrations with alembic upgrade commands. These commands mutate database schema and can break production systems if misused.
| `alembic init alembic` | Initialize Alembic in project |
The line documents an Alembic CLI command that creates migration files in the project. It is expected for this skill, but it is still an external command that should require user approval.
| `alembic revision --autogenerate -m "message"` | Generate migration from model changes |
The line instructs use of alembic revision with autogeneration, which writes migration files based on model state. This is legitimate but can create unsafe schema changes if not reviewed.
The line instructs use of alembic revision to create migration files. This is expected migration tooling, but it modifies the repository and should be reviewed.
The fenced bash example contains alembic init alembic, which creates migration scaffolding in the project. It is an expected command but still an external write operation.
The fenced bash example contains alembic revision commands that create migration files. Autogenerated migrations can include unintended schema changes if not reviewed.
The fenced bash example runs alembic revision --autogenerate, which writes migration files. The command is legitimate but requires review before applying.
03
Risk findings
Confirmed security concerns are separated from items that still need review.
The skill includes downgrade-to-base, drop table, drop column, drop type, and bulk update examples. These operations can delete or corrupt production data without backup and approval controls.
The cited lines explicitly describe downgrade base and drop operations. These are legitimate migration actions, but the data-loss risk is clear and high impact.
The examples show database connection URLs with user and password placeholders inside configuration. This can normalize storing credentials in committed files instead of secret-managed configuration.
The values appear to be placeholders, not real secrets. The risk is guidance quality because users may copy the pattern into project files.
04
Remediation
Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.
FIX-001
High
Destructive rollback and drop examples
Require backups, restore tests, and production approval before downgrade base, drop table, drop column, or drop type examples.
FIX-002
High
Misleading no data loss checklist item
Replace drop-based no-data-loss guidance with additive migrations, backfills, archival plans, and verified rollback limits.
FIX-003
Medium
Mutable Alembic command guidance
State that upgrade, downgrade, and revision commands require explicit user approval and environment confirmation before execution.
FIX-004
Medium
Plaintext database URL examples
Replace user:pass connection strings with environment-variable or secret-manager placeholders.
05
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.