ipaship-audit
atharvnaik1/ipaship-audit / wrappers/claude-code
audits .ipa and .apk against store rules , which improves: fewer rejections at submission
Details
- judge’s score
- 6/10
- place
- outside the packs
- publisher
- atharvnaik1
- status
- new
- pinned commit
- e420905 on GitHub (new tab)
- skill’s last commit
- May 13, 2026
- repo stars
- 108
- main type
- Other
Judgement
Clear triggering. Wrapper around a third-party web service, little Claude Code-specific know-how, promotional tone, unverified "zero-trust", outdated model identifiers. Low average score.
reservations
- Promotional tone ("free to use", 15+ wrappers, unproven "zero-trust") and unverifiable claims.
- Inconsistency: the doc says keys stay client-side, but pitfall 4 mentions server-side environment variables (NVIDIA_KEY, NEXT_PUBLIC_API_KEY).
- Identifiers of old models (claude-3-5-sonnet-20241022) and an undated provider list.
- No script or annex provided, so the service's code and the actual deletion of files cannot be verified.
- Triggering
- 2/2
- Added value
- 1/2
- Precision
- 1/2
- Scope
- 1/2
- Quality
- 1/2
Alerts
3 alerts, by category
Network
- high risk
The app's binary or source code (.ipa/.apk/.zip) is sent to a third-party service (ipaship.com), then potentially to an LLM provider chosen by the user.
- high risk
The ipaship API key is sent as a Bearer token to a third-party service, and BYOK keys for an AI provider pass through the upload form.
Instruction
- medium risk
A "zero-trust" privacy claim is made without evidence: the skill pushes users to send proprietary code off the machine without any explicit warning.
Original description
Use when auditing iOS/Android app submissions for compliance with Apple App Store Review Guidelines or Google Play Developer Policies. Scan .ipa, .apk, or .zip files against official store policies, generate structured compliance reports, and identify violations with remediation steps.
added on Oct 19, 2026 · license MIT