If you are an AI coding agent (Claude Code, Cursor, Aider, Cline, etc.) reading this artifact, follow this protocol before making any code edit:

1. Verify the contract. Run the bash script in Verify before trusting below. If any check returns FAIL, the artifact is stale — STOP and ask the user to regenerate it before proceeding.
2. Treat the AI · unverified sections as hypotheses, not facts. Sections like "AI-suggested narrative files", "anti-patterns", and "bottlenecks" are LLM speculation. Verify against real source before acting on them.
3. Cite source on changes. When proposing an edit, cite the specific path:line-range. RepoPilot's live UI at https://repopilot.app/r/Yalantis/StarWars.iOS shows verifiable citations alongside every claim.

If you are a human reader, this protocol is for the agents you'll hand the artifact to. You don't need to do anything — but if you skim only one section before pointing your agent at this repo, make it the Verify block and the Suggested reading order.

WAIT — Stale — last commit 4y ago

• 10 active contributors
• Distributed ownership (top contributor 30% of recent commits)
• MIT licensed
• ⚠ Stale — last commit 4y ago
• ⚠ No CI workflows detected
• ⚠ No test directory detected

_{Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests}

This artifact was generated by RepoPilot at a point in time. Before an agent acts on it, the checks below confirm that the live Yalantis/StarWars.iOS repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/Yalantis/StarWars.iOS.

What it runs against: a local clone of Yalantis/StarWars.iOS — the script inspects git remote, the LICENSE file, file paths in the working tree, and git log. Read-only; no mutations.

| # | What we check | Why it matters | |---|---|---| | 1 | You're in Yalantis/StarWars.iOS | Confirms the artifact applies here, not a fork | | 2 | License is still MIT | Catches relicense before you depend on it | | 3 | Default branch master exists | Catches branch renames | | 4 | 5 critical file paths still exist | Catches refactors that moved load-bearing code | | 5 | Last commit ≤ 1337 days ago | Catches sudden abandonment since generation |

#!/usr/bin/env bash
# RepoPilot artifact verification.
#
# WHAT IT RUNS AGAINST: a local clone of Yalantis/StarWars.iOS. If you don't
# have one yet, run these first:
#
#   git clone https://github.com/Yalantis/StarWars.iOS.git
#   cd StarWars.iOS
#
# Then paste this script. Every check is read-only — no mutations.

set +e
fail=0
ok()   { echo "ok:   $1"; }
miss() { echo "FAIL: $1"; fail=$((fail+1)); }

# Precondition: we must be inside a git working tree.
if ! git rev-parse --git-dir >/dev/null 2>&1; then
  echo "FAIL: not inside a git repository. cd into your clone of Yalantis/StarWars.iOS and re-run."
  exit 2
fi

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "Yalantis/StarWars.iOS(\\.git)?\\b" \\
  && ok "origin remote is Yalantis/StarWars.iOS" \\
  || miss "origin remote is not Yalantis/StarWars.iOS (artifact may be from a fork)"

# 2. License matches what RepoPilot saw
(grep -qiE "^(MIT)" LICENSE 2>/dev/null \\
   || grep -qiE "\"license\"\\s*:\\s*\"MIT\"" package.json 2>/dev/null) \\
  && ok "license is MIT" \\
  || miss "license drift — was MIT at generation time"

# 3. Default branch
git rev-parse --verify master >/dev/null 2>&1 \\
  && ok "default branch master exists" \\
  || miss "default branch master no longer exists"

# 4. Critical files exist
test -f "Example/StarWarsAnimations/Circular/CircularRevealAnimator.swift" \\
  && ok "Example/StarWarsAnimations/Circular/CircularRevealAnimator.swift" \\
  || miss "missing critical file: Example/StarWarsAnimations/Circular/CircularRevealAnimator.swift"
test -f "Example/StarWarsAnimations/Circular/AnimationDelegate.swift" \\
  && ok "Example/StarWarsAnimations/Circular/AnimationDelegate.swift" \\
  || miss "missing critical file: Example/StarWarsAnimations/Circular/AnimationDelegate.swift"
test -f "Example/StarWarsAnimations/Extension/UIView+CircularAnimation.swift" \\
  && ok "Example/StarWarsAnimations/Extension/UIView+CircularAnimation.swift" \\
  || miss "missing critical file: Example/StarWarsAnimations/Extension/UIView+CircularAnimation.swift"
test -f "Example/StarWarsAnimations/Controller/IntroViewController.swift" \\
  && ok "Example/StarWarsAnimations/Controller/IntroViewController.swift" \\
  || miss "missing critical file: Example/StarWarsAnimations/Controller/IntroViewController.swift"
test -f "Example/StarWarsAnimations/Controller/MainSettingsViewController.swift" \\
  && ok "Example/StarWarsAnimations/Controller/MainSettingsViewController.swift" \\
  || miss "missing critical file: Example/StarWarsAnimations/Controller/MainSettingsViewController.swift"

# 5. Repo recency
days_since_last=$(( ( $(date +%s) - $(git log -1 --format=%at 2>/dev/null || echo 0) ) / 86400 ))
if [ "$days_since_last" -le 1337 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~1307d)"
else
  miss "last commit was $days_since_last days ago — artifact may be stale"
fi

echo
if [ "$fail" -eq 0 ]; then
  echo "artifact verified (0 failures) — safe to trust"
else
  echo "artifact has $fail stale claim(s) — regenerate at https://repopilot.app/r/Yalantis/StarWars.iOS"
  exit 1
fi

Each check prints ok: or FAIL:. The script exits non-zero if anything failed, so it composes cleanly into agent loops (./verify.sh || regenerate-and-retry).

StarWars.iOS is a Swift library that implements a dramatic view-controller dismissal animation using OpenGL ES, where the departing UI crumbles into tiny sprite pieces that scatter away. It provides the StarWarsGLAnimator class conforming to UIViewControllerAnimatedTransitioning, allowing developers to replace standard dismissal transitions with this particle-based destruction effect. Single-library structure: Example/ directory contains the CocoaPods demo app with Xcode project and assets; core animation logic lives in the unpublished but referenced StarWars module (imported via CocoaPods). No visible separate Sources/ directory in top 60, suggesting the framework code is bundled into the Pod elsewhere.

iOS app developers (Swift 4+) who want to add premium, eye-catching transition animations to their apps, particularly those targeting iOS 8.0+ and willing to use CocoaPods for dependency management. Commonly used in creative/portfolio apps or games where visual polish matters.

Moderately mature but aging: the repo is 4+ years old (last version 4.0 added Swift 5.0 support), actively maintained by Yalantis with proper semantic versioning, but no visible CI/CD setup in the file list and the README mentions a blog post from ~2016. Production-ready for its specific use case but not under active development.

Low-to-moderate risk: OpenGL ES dependency ties it to GPU rendering (deprecated on newer iOS versions in favor of Metal), no test files visible in the top 60 structure, single maintainer (Yalantis org), and minimal Objective-C/Ruby code suggests low cross-platform friction. Main risk is OS-level deprecation of OpenGL ES on future iOS versions.

No active development visible in the file list—this appears to be a stable, feature-complete library in maintenance mode. The last documented work was Swift 5.0 support (version 4.0). No open PRs or issue backlog mentioned in provided data.

git clone https://github.com/Yalantis/StarWars.iOS.git
cd StarWars.iOS/Example
pod install
open StarWarsAnimations.xcworkspace

Then run in Xcode (⌘R) to see the crumble animation demo.

Daily commands: Open Example/StarWarsAnimations.xcworkspace in Xcode and press ⌘R. The example app demonstrates the animation by presenting/dismissing view controllers with the StarWarsGLAnimator attached as the transitioningDelegate.

• Example/StarWarsAnimations/Circular/CircularRevealAnimator.swift — Core animator implementing the crumble/reveal transition effect; every contributor must understand this to modify animation behavior
• Example/StarWarsAnimations/Circular/AnimationDelegate.swift — UIViewControllerTransitioningDelegate implementation that wires the animator into UIKit's transition system; entry point for custom transitions
• Example/StarWarsAnimations/Extension/UIView+CircularAnimation.swift — UIView extension adding circular animation capabilities; fundamental to how views are transformed during the crumble transition
• Example/StarWarsAnimations/Controller/IntroViewController.swift — Example usage demonstrating how to apply the StarWars transition animation to a real view controller
• Example/StarWarsAnimations/Controller/MainSettingsViewController.swift — Settings UI showing animation configuration options; reveals the customization API and parameter exposure
• Example/StarWarsAnimations/Extension/UIView+IBInspectable.swift — IBInspectable properties for design-time configuration in Interface Builder; shows how animation parameters are exposed to developers

• CircularRevealAnimator (Core Animation, CABasicAnimation, CAAnimationGroup) — Orchestrates the entire crumble animation: calculates duration, creates CABasicAnimation objects for each particle fragment, applies transforms (scale, rotation, opacity), and commits animations to the layer tree
  • Failure mode: If animation duration is too short, particles may not fully animate; if transform calculations are wrong, fragments appear in incorrect positions or fail to fade out
• AnimationDelegate (UIKit, UIViewControllerTransitioningDelegate) — Implements UIViewControllerTransitioningDelegate protocol; returns CircularRevealAnimator instance on demand when a view controller dismissal is triggered
  • Failure mode: If delegate is not assigned to transitioningDelegate property or returns nil, standard default dismissal animation is used instead
• UIView+CircularAnimation extension (Core Animation, CALayer, CAShapeLayer) — Adds helper methods to any UIView for applying circular masks, calculating particle positions, and initiating animations
  • Failure mode: If mask geometry calculations fail, the circular reveal mask may not align with the view bounds, breaking the visual effect
• Example View Controllers (UIViewController, UIKit, Storyboard) — IntroViewController and MainSettingsViewController demonstrate instantiation and configuration of the animation delegate; serve as reference for developers integrating the component
  • Failure mode: If transitioningDelegate is not set or is set incorrectly, no custom animation is applied on dismissal

• User interaction (dismiss gesture) → UIViewController transitioningDelegate — User gesture triggers view controller dismissal; UIKit calls transitioningDelegate to obtain animator
• UIViewController transitioningDelegate → CircularRevealAnimator — Delegate returns animator instance configured with animation parameters
• CircularRevealAnimator → Core Animation (CABasicAnimation) — Animator creates and adds CABasicAnimation objects to view layer; specifies keyframes for scale, rotation, position, and opacity
• Core Animation → GPU rendering — CADisplayLink synchronizes animation updates with display refresh rate; GPU renders each frame
• GPU rendering → Screen display — Rendered frames composited and displayed; user sees crumble particle effect
• Animation completion callback → UIViewController transition context — undefined

Create a custom transition animator

1. Create a new Swift file inheriting from NSObject and conforming to UIViewControllerAnimatedTransitioning (Example/StarWarsAnimations/Circular/CircularRevealAnimator.swift)
2. Implement transitionDuration(:) and animateTransition(:) methods, using CABasicAnimation or CAKeyframeAnimation for the effect (Example/StarWarsAnimations/Circular/CircularRevealAnimator.swift)
3. Create a delegate class conforming to UIViewControllerTransitioningDelegate that returns your animator from animationControllerForDismissedController(_:) (Example/StarWarsAnimations/Circular/AnimationDelegate.swift)
4. Assign the delegate to a UIViewController's transitioningDelegate property and set modalPresentationStyle to .custom (Example/StarWarsAnimations/Controller/IntroViewController.swift)

Add a new animatable property to UIView

1. Open the UIView extension file (Example/StarWarsAnimations/Extension/UIView+CircularAnimation.swift)
2. Add a computed property or method that applies Core Animation changes (layer properties, CADisplayLink, or CAAnimationGroup) (Example/StarWarsAnimations/Extension/UIView+CircularAnimation.swift)
3. If you want it configurable in Interface Builder, add an @IBInspectable property to the UIView extension (Example/StarWarsAnimations/Extension/UIView+IBInspectable.swift)

Expose a new animation parameter to the demo app UI

1. Add a UISwitch, UISlider, or UISegmentedControl to the storyboard (Example/StarWarsAnimations/Base.lproj/Main.storyboard)
2. Create an IBOutlet and IBAction in MainSettingsViewController to capture the control value (Example/StarWarsAnimations/Controller/MainSettingsViewController.swift)
3. Pass the parameter value to the CircularRevealAnimator when setting up the transitioningDelegate (Example/StarWarsAnimations/Circular/CircularRevealAnimator.swift)

• UIViewControllerTransitioningDelegate & UIViewControllerAnimatedTransitioning — iOS standard API for custom view controller transition animations; allows clean separation of animation logic from view controller code
• Core Animation (CABasicAnimation, CAKeyframeAnimation, CADisplayLink) — Provides high-performance, GPU-accelerated animation primitives needed for smooth particle effects without blocking the main thread
• Swift with UIKit — Primary iOS framework for UI; Swift enables type-safe extension patterns and modern syntax for the animation code
• IBInspectable properties — Allows designers and developers to tweak animation parameters directly in Interface Builder without code changes, reducing iteration time

• Particle crumble effect using multiple CABasicAnimations rather than custom rendering (OpenGL/Metal)

  • Why: Balances visual quality with development simplicity; easier to maintain and debug than low-level graphics code
  • Consequence: May have slight performance impact on older devices with many simultaneous particle animations, but acceptable for typical UI transitions

• Transition animation tightly coupled to view controller dismiss gesture via transitioningDelegate

  • Why: Follows UIKit conventions; integrates seamlessly with standard iOS navigation flows
  • Consequence: Requires explicit delegate assignment on each view controller; not globally applicable without wrapper code

• Example app in same project as library code

  • Why: Simplifies development workflow; example always stays in sync with library API changes
  • Consequence: Example app code and library code not cleanly separated in repository structure

• Does not support presentation animations (only dismissal); focused on exit transitions
• Not a cross-platform animation library; iOS-only
• Does not handle interactive gestures (pan/swipe-driven animation); fixed-duration transition only
• Does not provide real-time physics simulation; uses pre-computed Core Animation curves

• OpenGL ES deprecation: iOS 12+ prefers Metal over OpenGL ES; future iOS versions may break rendering. - GPU memory overhead: sprite count scales with view size; large screens or rapid re-dismissals may exhaust GPU memory. - Framework code not in repo: the actual StarWars module source is not visible in Example/ or top 60 files—likely distributed only as a built Pod binary, making source-level debugging or contribution harder. - No CocoaPods Podspec in file list: verify the .podspec file exists in root to confirm Pod distribution setup.

• UIViewControllerTransitioningDelegate — Core UIKit protocol that intercepts view-controller lifecycle events to inject custom animations; essential for understanding how StarWarsGLAnimator hooks into dismissal
• OpenGL ES 2.0 Particle Effects — The library renders crumbling sprites using GPU-accelerated point sprites or quads; understanding ES 2.0 shader basics explains why duration/spriteWidth tune the visual effect
• CADisplayLink (Frame Synchronization) — Likely used internally to sync animation frames with screen refresh rate (60/120 Hz), ensuring smooth crumble effect without stutter
• Custom UIViewControllerAnimatedTransitioning — Protocol requiring animateTransition(using:) implementation; StarWarsGLAnimator conforms to this to define the crumble animation timeline and completion semantics
• Sprite Sheet / Texture Atlas — The crumble animation likely pre-bakes a snapshot of the view into GPU texture memory, then fragments it into a grid of sprites; efficient batch rendering via atlas reduces draw calls
• Physics-Based Animation (UIKit Dynamics analog) — Blog post reference suggests gravity, friction, or impulse may drive sprite motion during crumble; understanding UIDynamics concepts helps customize animator behavior

• Yalantis/PullToRefresh — Sister Yalantis animation library demonstrating similar high-polish, GPU-accelerated UI transitions for iOS
• Yalantis/Side-Menu.iOS — Companion Yalantis UI component showing modal/dismissal animation patterns that pair well with StarWars for navigation flows
• ramotion/roulette-wheel — Similar custom iOS transition animation library using CoreAnimation instead of OpenGL, useful comparison for animation strategy trade-offs
• Yalantis/Koloda — Yalantis card-stack animation library; same team, same architectural patterns for gesture-driven transition animations
• Interactive-Studio/Windless — Unrelated but shows alternative shimmer/particle animation patterns in Swift that could inspire OpenGL→Metal modernization

To work on one of these in Claude Code or Cursor, paste: Implement the "<title>" PR idea from CLAUDE.md, working through the checklist as the task list.

Add Swift Package Manager support with Package.swift manifest

The repo currently only supports CocoaPods installation. Adding SPM support would modernize the project and make it accessible to developers using Swift Package Manager, which is now the recommended dependency manager for Swift projects. This is a high-value addition given the repo targets Swift 4+ and Xcode 8+.

• [ ] Create Package.swift file in the root directory with proper product and target definitions
• [ ] Reference the core animation source files (likely in a StarWars/ or Sources/ directory based on the pod structure)
• [ ] Test SPM integration by adding the package via Xcode's 'Add Packages' feature
• [ ] Update README.md with Swift Package Manager installation instructions

Add unit and snapshot tests for StarWars transition animations

The repo contains complex animation logic for the crumbling transition effect but has no visible test files. Adding unit tests for animation parameters and snapshot tests for the visual effect would improve code reliability and prevent regressions. This is especially important for animation libraries where visual correctness matters.

• [ ] Create Tests/ directory structure mirroring the source layout
• [ ] Add unit tests for animation controller initialization and configuration in the main animation class
• [ ] Add snapshot tests using a library like SnapshotTesting to capture the crumbling effect behavior
• [ ] Set up test targets in Example/StarWarsAnimations.xcodeproj/project.pbxproj
• [ ] Document test running instructions in README.md or contributing.md

Create GitHub Actions CI workflow for Swift/iOS builds and tests

The .github directory exists with issue templates but lacks a CI workflow file. Adding a GitHub Actions workflow for building and testing on iOS will catch integration issues early and improve code quality. This provides automated validation on every PR.

• [ ] Create .github/workflows/ci.yml with steps to checkout, build the example project, and run tests
• [ ] Configure the workflow to use xcodebuild to build Example/StarWarsAnimations.xcodeproj for iOS simulator
• [ ] Add test execution step (if tests are added via the previous PR idea)
• [ ] Set the workflow to trigger on push and pull_request events
• [ ] Update .github/contributing.md to mention that CI checks must pass before merging

• Add unit tests for StarWarsGLAnimator initialization and customization (duration, spriteWidth properties) in a new Tests/ folder, since none are visible in the top 60 files.
• Create a migration guide document in docs/ explaining how to replace OpenGL ES rendering with Metal for iOS 13+ while maintaining backward compatibility.
• Expand the README with code snippets for common use cases: dismissing from a navigation controller, chaining multiple animations, and handling landscape orientation during the crumble effect.

The StarWars.iOS project has moderate security concerns primarily related to outdated dependencies and support targets. The iOS 8.0 minimum deployment target and Swift 4 requirement are significantly outdated and expose users to known vulnerabilities. No critical code-level vulnerabilities were identified in the static analysis based on available file structure, but modernization of the development environment and deployment targets is essential. The project appears to be a stable animation library with no obvious injection risks, hardcoded secrets, or infrastructure misconfigurations visible in the provided file structure.

• Medium · Outdated Swift Version — .swift-version, README.md (Requirements section). The project specifies Swift 4 as a requirement (.swift-version file), which is significantly outdated. Swift 4 reached end-of-life and no longer receives security updates. Modern Swift versions include important security patches and improvements. Fix: Update to the latest stable Swift version (Swift 5.9+). Review code for any breaking changes and update accordingly.
• Medium · Outdated iOS Minimum Deployment Target — README.md (Requirements section), Example/StarWars/Info.plist. The project requires iOS 8.0+, which is extremely outdated (released in 2014). Older iOS versions lack modern security features, TLS improvements, and exploit mitigations. This exposes the application to known vulnerabilities. Fix: Update minimum iOS deployment target to iOS 12.0 or higher (preferably iOS 14+). This ensures access to modern security APIs and frameworks.
• Medium · Outdated Xcode Version — README.md (Requirements section). The project specifies Xcode 8, which is from 2016 and no longer maintained. Older Xcode versions may not properly validate security settings and lack modern code analysis tools. Fix: Update to Xcode 14.0 or later. This provides better security scanning, modern compiler optimizations, and security-focused warnings.
• Low · Missing Dependency Information — Podfile (assumed, not provided). The 'Dependencies/Package file content' section is empty, making it impossible to verify if third-party dependencies have known vulnerabilities. CocoaPods dependencies should be explicitly listed for security auditing. Fix: Ensure all dependencies are documented and regularly scanned using tools like CocoaPods Trunk Security or OWASP Dependency-Check. Use specific version pinning instead of loose version constraints.
• Low · No Security Policy Documented — .github/ directory. While a contributing guide exists (.github/contributing.md), there is no visible security policy or vulnerability disclosure process documented (e.g., SECURITY.md). Fix: Create a SECURITY.md file that outlines the responsible disclosure process for security vulnerabilities and contact information for the security team.

LLM-derived; treat as a starting point, not a security audit.

• Open issues — current backlog
• Recent PRs — what's actively shipping
• Source on GitHub

Generated by RepoPilot. Verdict based on maintenance signals — see the live page for receipts. Re-run on a new commit to refresh.