T08 · Insecure Dependencies
Warning
- Location
SKILL.md:58- Finding
Unpinned Third-Party Package Installation and Execution
- Content
View full analysis
npx prisma migrate deploy npx prisma migrate reset npx prisma migrate status npx prisma generate npx prisma db seed npx prisma db pull npx prisma db push ``` ```bash # SKILL.md:100-115 npx drizzle-kit generate npx drizzle-kit migrate npx drizzle-kit push npx drizzle-kit pull npx drizzle-kit studio npx drizzle-kit check ``` ```bash # SKILL.md:129-147 npx knex migrate:make npx knex migrate:latest npx knex migrate:rollback npx knex migrate:rollback --all npx knex migrate:status npx knex seed:run npx knex seed:make ``` ```bash # SKILL.md:168-180 npx typeorm migration:generate -d src/data-source.ts src/migrations/ npx typeorm migration:create src/migrations/ npx typeorm migration:run -d src/data-source.ts npx typeorm migration:revert -d src/data-source.ts npx typeorm migration:show -d src/data-source.ts ``` ```bash # SKILL.md:344-354 npx prisma db pull npx drizzle-kit check npx drizzle-kit pull ``` ```bash # SKILL.md:377 pip install migra ``` ### Technical Analysis The Skill directs the Agent to execute multiple Node.js command-line packages through `npx` and to install `migra` through `pip` without specifying exact versions or requiring integrity and provenance verification. When the requested executable is not already present in the project, `npx` can retrieve a package from the configured package registry and execute its installation scripts or command-line entry point. Likewise, `pip install migra` resolves the package version from mutable registry metadata at execution time. The effective code executed by these commands can therefore differ from the code that existed when the Skill was audited. Th ...[truncated 2254 chars]- Remediation
View remediation
--hash=sha256: ``` Install it using: ```bash python -m pip install --require-hashes -r requirements-tools.txt ``` 6. Use an approved internal registry or repository proxy with package allowlisting, malware scanning, immutable artifacts, and provenance verification. 7. Run migration tooling in a sandbox or isolated container with minimal filesystem and network access. 8. Give migration processes narrowly scoped database accounts. Separate read-only schema inspection, migration, backup, and administrative credentials where practical. 9. Do not expose production environment files to package installation processes. Resolve and install reviewed tooling before injecting database credentials. 10. Document a verification step requiring the Agent to confirm that the executable is a lockfile-controlled local dependency before running it. ]]>