T08 · Insecure Dependencies
- Location
mobile.md:13- Finding
Unpinned Fastlane Installation Exposes the Build Environment to Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is documentation-only and relevant to CI/CD, but its reusable workflow examples include unsafe deployment patterns that merit review before installation.
Review and harden any workflow before copying it into a repository. In particular, pin third-party actions to reviewed commits, avoid exposing secrets to pull-request jobs, add minimal permissions and environment approvals, restrict deployment keys and sudo rights, and confirm whether Docker images or mobile artifacts will be published automatically.
mobile.md:13Unpinned Fastlane Installation Exposes the Build Environment to Supply-Chain Risk
mobile.md:91Flutter CI Action Is Referenced Through a Mutable Version Tag
web.md:96Mutable Third-Party Deployment Actions Receive Production SSH Credentials
web.md:57Pull-Request Branch Name Is Interpolated Directly into Shell Source
The trigger list contains broad, common phrases such as 'build failing' and 'deploy automatically' that can match many ordinary developer conversations. This increases the chance of unintended skill activation, which can cause the agent to apply CI/CD-specific guidance in the wrong context or too eagerly in adjacent tasks.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
| Stack | Recommended | Why |
|-------|-------------|-----|
| Web (Next.js, Nuxt, static) | Vercel, Netlify | Zero-config, auto-deploys, preview URLs |
| Mobile (iOS/Android/Flutter) | Codemagic, Bitrise + Fastlane | Pre-configured signing, app store upload |
| Backend/Docker | GitHub Actions, GitLab CI | Full control, self-hosted runners option |
| Monorepo | Nx/Turborepo + GHA | Affected detection, build caching |
The Docker template includes an authenticated login and unconditionally pushes built images to a remote registry on pushes to main, but does not clearly warn users that it will publish artifacts externally using repository-scoped credentials. In a copy-paste template skill, that omission can cause accidental public or organizational image publication, potentially exposing proprietary code, configuration, or sensitive build outputs.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
host: ${{ secrets.SSH_HOST }} username: ${{ secrets.SSH_USER }} key: ${{ secrets.SSH_KEY }} script: sudo systemctl restart myapp
## Common Issues
No suspicious patterns detected.