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/icanzilb/EasyAnimation 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 5y ago

• 18 active contributors
• MIT licensed
• ⚠ Stale — last commit 5y ago
• ⚠ Concentrated ownership — top contributor handles 79% of recent commits
• ⚠ 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 icanzilb/EasyAnimation repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/icanzilb/EasyAnimation.

What it runs against: a local clone of icanzilb/EasyAnimation — 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 icanzilb/EasyAnimation | 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 | Last commit ≤ 2017 days ago | Catches sudden abandonment since generation |

#!/usr/bin/env bash
# RepoPilot artifact verification.
#
# WHAT IT RUNS AGAINST: a local clone of icanzilb/EasyAnimation. If you don't
# have one yet, run these first:
#
#   git clone https://github.com/icanzilb/EasyAnimation.git
#   cd EasyAnimation
#
# 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 icanzilb/EasyAnimation and re-run."
  exit 2
fi

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "icanzilb/EasyAnimation(\\.git)?\\b" \\
  && ok "origin remote is icanzilb/EasyAnimation" \\
  || miss "origin remote is not icanzilb/EasyAnimation (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"

# 5. Repo recency
days_since_last=$(( ( $(date +%s) - $(git log -1 --format=%at 2>/dev/null || echo 0) ) / 86400 ))
if [ "$days_since_last" -le 2017 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~1987d)"
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/icanzilb/EasyAnimation"
  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).

EasyAnimation is a Swift library that extends UIView.animateWithDuration() to animate CALayer properties directly within animation blocks, eliminating boilerplate CABasicAnimation code. It adds support for spring animations, chainable sequences, and mixed view/layer animations while maintaining the familiar UIKit animation API syntax. Simple flat structure: Core logic in EasyAnimation/EasyAnimation.swift and EasyAnimation/EAAnimationFuture.swift, spring physics in EasyAnimation/RBBSpringAnimation/ (vendored), comprehensive demo app in DemoApp/ with storyboards and view controllers, and playground examples in EasyAnimationDemo.playground/Pages/.

iOS/tvOS developers building animation-heavy UIs who want to animate layer properties (position, opacity, transform) without writing CABasicAnimation boilerplate, particularly those already comfortable with UIView animation blocks.

Mature and stable. The project has reached v2.0 with intentional breaking changes (requiring explicit EasyAnimation.enable() call), comprehensive demo app with 4 animation example ViewControllers, and a playground with working examples. However, the repo appears archived or lightly maintained—no recent commit dates visible in the file listing, and the README warns it 'does NOT automatically install itself' in v2.0, suggesting deliberate design for compatibility rather than active development.

Low risk for stable use; moderate risk for active development. The library has no external dependencies except the bundled RBBSpringAnimation (Apache 2.0), reducing supply-chain risk. The single-maintainer status (icanzilb) and apparent inactive state mean security patches and Swift version compatibility updates may lag. No visible test suite in the file listing is a notable gap. The opt-in enable() pattern in v2.0 mitigates accidental breaking changes.

No active development signals visible from the file listing. The repo appears to be in maintenance mode post-v2.0, with the last meaningful work being the breaking changes to require explicit enable() and comprehensive playground + demo coverage. No open PRs, milestones, or recent commits are evident.

Clone the repo, open EasyAnimation.xcodeproj in Xcode, and run the DemoApp target:

git clone https://github.com/icanzilb/EasyAnimation.git
cd EasyAnimation
open EasyAnimation.xcodeproj
# Select DemoApp scheme, build and run on simulator

Alternatively, explore EasyAnimationDemo.playground in Xcode (File > Open) for interactive examples without running the full app.

Daily commands: Open DemoApp/DemoApp.xcodeproj, select DemoApp scheme, press Cmd+R in Xcode. Tap through 4 tabs (Chains, Layer/View Animations, Multiple Animations, Spring Animations) to see live demos. For playground: open EasyAnimationDemo.playground, select a page (Chains.xcplaygroundpage, Spring Animation.xcplaygroundpage, etc.), and run timeline in the assistant editor.

• EasyAnimation/EasyAnimation.swift: Core library: extends UIView.animate via method swizzling to intercept and auto-animate layer property changes
• EasyAnimation/EAAnimationFuture.swift: Implements chainable animation API and completion block handling for sequential animations
• EasyAnimation/RBBSpringAnimation/RBBSpringAnimation.swift: Vendored spring physics engine; powers spring animation curves with configurable damping and stiffness
• DemoApp/DemoApp/DemoChainsViewController.swift: Concrete example of chaining animations sequentially using the library API
• DemoApp/DemoApp/DemoSpringAnimationsViewController.swift: Demonstrates spring animation parameters (damping, stiffness, mass) in action
• [EasyAnimationDemo.playground/Pages/Spring Animation.xcplaygroundpage/Contents.swift](https://github.com/icanzilb/EasyAnimation/blob/master/EasyAnimationDemo.playground/Pages/Spring Animation.xcplaygroundpage/Contents.swift): Interactive playground for learning spring animation behavior without running the full app

Start by examining EasyAnimation/EasyAnimation.swift—this is the main extension point on UIView.animate. EAAnimationFuture.swift handles chainable animations and completion blocks. To add new animation types, hook into the CABasicAnimation creation logic in EasyAnimation.swift. Add demo ViewControllers in DemoApp/DemoApp/.swift and playground pages in EasyAnimationDemo.playground/Pages//Contents.swift. Spring animations are in RBBSpringAnimation/RBBSpringAnimation.swift.

Critical: Must call EasyAnimation.enable() once at app startup (e.g., AppDelegate.application:didFinishLaunchingWithOptions:) or animations will not work—the library uses opt-in method swizzling. No visible test suite means breaking changes in Swift compiler versions may not be caught. The library assumes CALayer animation interception at runtime; conflicts possible with other animation libraries that also swizzle UIView methods. tvOS support exists (Info-tvOS.plist, xcscheme) but is less commonly tested; verify on actual tvOS device if targeting it.

• Method Swizzling (Runtime Introspection) — EasyAnimation uses Objective-C runtime method_exchangeImplementations to intercept UIView.animate calls—understanding this is essential to grasping how the library works without explicit wrappers
• CABasicAnimation vs Implicit Animations — Core distinction: EasyAnimation converts property writes (view.layer.position.x = 200) into CABasicAnimation objects automatically; learners must understand both explicit and implicit layer animation models
• Spring Physics (Damping, Stiffness, Mass) — RBBSpringAnimation models spring motion via differential equations; tuning these parameters in DemoSpringAnimationsViewController is key to realistic motion but unintuitive without physics background
• CATransaction and Implicit Transactions — UIView.animate wraps layer changes in CATransaction; EasyAnimation must manage transaction lifetime and timing to coordinate view and layer animations together
• Chainable/Fluent APIs (Method Chaining) — EAAnimationFuture enables sequential animation composition (anim1().then(anim2())); pattern borrowed from modern promise/async libraries, non-obvious in Swift closure context
• CAKeyframeAnimation — Used internally for complex animation chains; understanding keyframes is needed to debug multi-step animation behavior or extend the library

• CocoaPods/Masonry — Comparable DSL-based simplification of UIKit (AutoLayout), showing same philosophy of reducing boilerplate via expressive Swift APIs
• Realm/Realm-Swift — Ecosystem companion: both simplify common iOS tasks via method swizzling and runtime introspection; good examples of production-grade Swift libraries managing versioning and compatibility
• Alamofire/Alamofire — Equivalent popularity/maturity level in Swift ecosystem; shows how to build stable, single-purpose libraries with clear APIs and good documentation
• robb/RBBAnimation — Predecessor/inspiration: RBBSpringAnimation vendored directly from this repo; full context on original spring physics implementation
• facebook/pop — Competing animation engine (Objective-C era); EasyAnimation v1 was partly motivated by needing a simpler Swift alternative for layer animations

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 comprehensive unit tests for EasyAnimation.swift core functionality

The repo has a demo app and playgrounds but no visible test targets. Given that EasyAnimation is a critical animation library with complex chaining and layer animation logic, unit tests would ensure reliability. Tests should cover the main animation APIs, future chains, and the enable/disable mechanism introduced in v2.0.

• [ ] Create EasyAnimationTests target in EasyAnimation.xcodeproj
• [ ] Add tests in EasyAnimation/ directory for EasyAnimation.swift covering basic animations, layer animations, and chain operations
• [ ] Add tests for EAAnimationFuture.swift covering future creation, chaining, and cancellation
• [ ] Add tests verifying EasyAnimation.enable() properly initializes the library
• [ ] Create XCTest schemes and verify tests run in CI pipeline

Add Swift Package Manager support and GitHub Actions CI workflow

The repo has a podspec for CocoaPods but no Package.swift manifest for SPM adoption. Combined with no visible CI, adding both would modernize the distribution and catch regressions. The presence of tvOS scheme suggests multi-platform support that should be tested automatically.

• [ ] Create Package.swift manifest at repo root defining iOS and tvOS targets using existing EasyAnimation/ source files
• [ ] Add .github/workflows/swift.yml CI workflow to build and test on macOS for both iOS and tvOS platforms
• [ ] Verify playground sources (EasyAnimationDemo.playground/Sources) are excluded from package manifest
• [ ] Test that swift build and swift test work locally before pushing

Document spring animation API and parameters in README's Spring Layer Animations section

The README references a '#springs' section but the actual content is truncated. The RBBSpringAnimation.swift integration is a key feature but lacks explanation of parameters (damping, stiffness, mass, velocity). New users cannot understand how to use spring animations without API documentation.

• [ ] Expand the Spring Layer Animations section in README.md with code examples showing spring animation syntax
• [ ] Document all RBBSpringAnimation parameters: damping, stiffness, mass, velocity with typical values
• [ ] Cross-reference the EasyAnimationDemo.playground/Pages/Spring Animation.xcplaygroundpage example
• [ ] Add a comparison example showing spring animation vs standard animateWithDuration for clarity

• Add unit tests for EAAnimationFuture.swift: Create XCTest targets in EasyAnimation.xcodeproj to cover chain animation completion callbacks, sequence ordering, and error cases—currently no tests visible in file listing.
• Document spring animation parameter tuning: Add a guide markdown file explaining how stiffness/damping/mass values in RBBSpringAnimation.swift affect real-world animation feel, with before/after GIFs for common values (currently only implicit in DemoSpringAnimationsViewController).
• Add Swift Package Manager support: Create Package.swift manifest to allow swift package add installation alongside current CocoaPods only (EasyAnimation.podspec exists but no Package.swift).

The EasyAnimation library demonstrates a generally secure posture. It is a pure Swift animation framework with no external network dependencies, no database operations, and no obvious injection vectors. The code is straightforward UI animation logic without cryptographic concerns. Primary observations: (1) No critical vulnerabilities detected; (2) Third-party code (RBBSpringAnimation) is embedded rather than dependency-managed, which is manageable but suboptimal; (3) No evidence of hardcoded secrets or credentials; (4) No SQL, XSS, or similar injection risks present. The library is well-suited for App Store distribution as noted in the README. Recommended improvements focus on dependency management practices rather than security-critical issues.

• Low · Included Third-Party Spring Animation Library — EasyAnimation/RBBSpringAnimation/. The codebase includes RBBSpringAnimation, a third-party animation library embedded directly in the source tree. While the library itself appears legitimate, embedding third-party code without clear version tracking or dependency management increases maintenance burden and potential for outdated code with unpatched vulnerabilities. Fix: Consider using a dependency manager (CocoaPods, SPM, Carthage) to manage RBBSpringAnimation as an external dependency rather than embedding it. This allows for easier updates and security patches.
• Low · No Dependency Lock File Detected — Repository root. While a podspec file exists (EasyAnimation.podspec), no lock file (Podfile.lock, Package.resolved) is visible in the provided file structure. This makes it unclear if dependencies are pinned to specific versions, which could lead to inconsistent builds or unexpected updates. Fix: Ensure all dependency lock files are committed to version control to guarantee reproducible builds. For CocoaPods, maintain Podfile.lock; for SPM, maintain Package.resolved.
• Low · Playground Files Contain Executable Code — EasyAnimationDemo.playground/. The repository includes Xcode Playground files with executable Swift code (EasyAnimationDemo.playground/). Playgrounds can execute arbitrary code and may pose a risk if playgrounds from untrusted sources are opened. Fix: Document that users should review playground code before executing. Consider removing playgrounds from distributed packages or documenting their purpose clearly.

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.