T09 · Insecure Skill Coding Practices
- Location
upload-to-github.sh:19- Finding
Public Repository Upload Can Expose Sensitive Family Records
- Content
View full analysis
/dev/null; then echo "GitHub CLI detected; creating repository automatically..." gh repo create "$GITHUB_USER/$REPO_NAME" --public --description "$REPO_DESC" --source "." --push ``` ### Technical Analysis The script changes into a fixed Skill directory and executes `git add .`, which recursively stages every non-ignored file beneath that directory. It does not use an allowlist, verify the staged files, check for secrets or personal data, or confirm that generated family-memory content is excluded. When an authenticated GitHub CLI installation is present, the script creates a repository with `--public` and immediately pushes the staged content. This is especially unsafe in the context of this project because `SKILL.md` documents generated family-memory files and a photo library beneath the Skill directory. Such generated content can therefore be included in the same repository as the distributable project files. The manual instructions also explicitly recommend public visibility, so ...[truncated 1615 chars]- Remediation
View remediation
