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/Ramotion/expanding-collection 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 6y ago

• 17 active contributors
• Distributed ownership (top contributor 44% of recent commits)
• MIT licensed
• CI configured
• ⚠ Stale — last commit 6y ago
• ⚠ 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 Ramotion/expanding-collection repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/Ramotion/expanding-collection.

What it runs against: a local clone of Ramotion/expanding-collection — 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 Ramotion/expanding-collection | 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 ≤ 2255 days ago | Catches sudden abandonment since generation |

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

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "Ramotion/expanding-collection(\\.git)?\\b" \\
  && ok "origin remote is Ramotion/expanding-collection" \\
  || miss "origin remote is not Ramotion/expanding-collection (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 2255 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~2225d)"
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/Ramotion/expanding-collection"
  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).

ExpandingCollection is an iOS library that implements an animated material design card peek/pop controller, allowing users to tap a card to expand it with a smooth transition animation. It provides a BasePageCollectionCell subclass that handles the complex geometry and animation logic for transforming compact collection view cells into full-screen detail views without navigation controller overhead. Standard iOS framework structure: Source/ contains the core expanding collection view controller logic (implied by README), DemoExpandingCollection/ is a self-contained Xcode project demonstrating the library with hardcoded image assets (face1.png, boston.png, etc.) and an AppDelegate-rooted view hierarchy.

iOS app developers (Swift/Objective-C) building visually rich interfaces who need a reusable, production-ready card expansion UI pattern following material design guidelines. Particularly useful for portfolio apps, travel apps, or content browsers that want native animations rather than custom NavigationController transitions.

Moderately mature: the repo is well-established (evidenced by CocoaPods/Carthage support and CI via Travis), supports iOS 9.0+, and is written primarily in Swift (58KB). However, no explicit test files are visible in the file structure, and the last commit recency is unknown from the provided data—treat as 'stable but not heavily maintained.'

Low-to-medium risk: the library has minimal dependencies (just UIKit patterns), but the absence of visible unit tests and reliance on Xcode 9.0+ tooling creates a maintenance surface. Single-maintainer (Ramotion) scenario is typical for UI libraries but means breaking changes require external coordination. iOS 9.0 minimum is dated (current minimum is usually iOS 12+).

Unknown from provided data (no commit log or PR list visible). The file structure suggests this is a mature, feature-complete library in maintenance mode rather than active development.

git clone https://github.com/Ramotion/expanding-collection.git
cd expanding-collection
cd DemoExpandingCollection
open DemoExpandingCollection.xcodeproj
# In Xcode, select iPhone simulator and press Cmd+R to build and run

Daily commands: Open DemoExpandingCollection/DemoExpandingCollection.xcodeproj in Xcode 9.0+, select an iPhone simulator target, and press Cmd+R. The demo app will launch with a collection of card-like cells that expand on tap.

• DemoExpandingCollection/DemoExpandingCollection/AppDelegate.swift: Entry point for the demo app; shows how to instantiate and configure the expanding collection view controller.
• DemoExpandingCollection/DemoExpandingCollection/Assets.xcassets/: Contains all image assets (face1.png, boston.png, etc.) used by demo cells; modify here to change card backgrounds and icons.
• .swift-version: Specifies the Swift version constraint for the library and CocoaPods integration; check this before upgrading Xcode.

1. To customize cell appearance: edit the .xib file in DemoExpandingCollection/DemoExpandingCollection/ (look for cell definitions), respecting the width/height and centerY constraints. 2. To add new cell types: create a new UICollectionViewCell subclass inheriting from BasePageCollectionCell in Source/ (implied). 3. To adjust animation timing: the expansion logic likely lives in ExpandingCollectionViewController or similar in Source/ (not shown in file list).

1. Constraint precision required: the frontContainerView must have exactly width, height, centerX, and centerY constraints matching cellSize—missing or mismatched constraints will break the animation. 2. XIB file cell setup: cells are recommended to be created in XIB files (not programmatically), which requires careful outlet connections; missing @IBOutlet connections will cause runtime crashes. 3. iOS 9.0 minimum: older deployment target may cause issues in modern Xcode versions; consider updating if developing for iOS 12+.

• Material Design Motion — ExpandingCollection's core value proposition is implementing Material Design's shared element transition semantics; understanding motion principles helps customize animations effectively.
• UIView Geometry & Constraints — The library relies entirely on Auto Layout constraint manipulation to drive the expand/collapse animation; misunderstanding constraint interaction is the #1 source of bugs.
• CABasicAnimation & CAAnimationGroup — The smooth card expansion almost certainly uses Core Animation layer animations under the hood; knowing CABasicAnimation is essential for customizing timing curves and duration.
• UICollectionView Scrolling & Cell Lifecycle — ExpandingCollection overrides cell state during expand transitions; understanding when prepareForReuse() fires and cell visibility changes prevents animation glitches.
• XIB (Interface Builder) File Format — The recommended workflow uses XIB files for cell definitions; understanding XIB structure and outlet binding is mandatory for setup.
• Peek/Pop Interaction Model (3D Touch) — The library name references 'peek/pop' (iOS 3D Touch API); understanding this interaction helps position ExpandingCollection in the broader iOS gesture vocabulary.

• Ramotion/folding-cell — Companion Ramotion UI library for animated cell folding; shares the same material design philosophy and CocoaPods distribution pattern.
• Ramotion/gliding-collection — Another Ramotion library for animated collection view transitions; similar use case (card-based navigation) with different animation mechanics.
• AFNetworking/AFNetworking — Common dependency for loading images asynchronously in collection cells; many ExpandingCollection users pair this for dynamic content loading.
• realm/realm-swift — Frequently used for persisting collection view data (e.g., saved favorite cards) in iOS apps using ExpandingCollection.
• Ramotion/cardslider — Similar card-based UI pattern from Ramotion; explores horizontal card swiping as an alternative to vertical collection view expansion.

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 (SPM) support with Package.swift manifest

The repo lacks a Package.swift file for SPM distribution, making it harder for modern iOS projects to integrate ExpandingCollection. This is a high-value addition since SPM is now the preferred dependency manager for Swift packages. Currently, the library likely only supports CocoaPods/manual integration.

• [ ] Create Package.swift in the root directory with proper product and target definitions
• [ ] Ensure it references the existing ExpandingCollection source files correctly
• [ ] Test SPM integration by adding the repo as a package dependency in a test iOS project
• [ ] Update README.md with SPM installation instructions (add to existing installation section)

Create unit tests for core animation and view controller logic in ExpandingCollection framework

The repo structure shows DemoExpandingCollection but no dedicated Tests folder for the framework itself. Given that this library's core value is complex animations (peek/pop UI transitions), adding tests for animation timing, view state transitions, and controller lifecycle would prevent regressions and improve maintainability.

• [ ] Create Tests/ directory alongside the main ExpandingCollection framework source
• [ ] Add unit tests for the main peek/pop controller view model logic and state management
• [ ] Add tests for animation duration and timing curve verification
• [ ] Add tests for collection view delegate/datasource integration
• [ ] Integrate tests into .travis.yml to run on every commit

Add GitHub Actions CI workflow and migrate from Travis CI

The repo uses .travis.yml for CI, which is outdated. GitHub Actions is now the standard for GitHub repositories and provides better integration, faster execution, and no external account management needed. This modernizes the development workflow.

• [ ] Create .github/workflows/swift-build-test.yml with steps to build and test the library
• [ ] Include matrix testing for multiple iOS SDK versions (e.g., iOS 13, 14, 15+)
• [ ] Add SwiftLint or SwiftFormat step to enforce code quality standards
• [ ] Ensure workflow runs on push to main/master and on pull requests
• [ ] Document the migration in README.md's development section or CONTRIBUTING.md

• Add comprehensive unit test suite for BasePageCollectionCell animation logic—the repo shows no visible tests, making it hard to validate changes or prevent regressions.
• Document the exact constraint setup required in the README with a step-by-step screenshot guide or video; the current text-only instructions are vague and often trip up new users.
• Create a modern SwiftUI wrapper or sample using UIViewControllerRepresentable to demonstrate how to integrate this UIKit library into modern SwiftUI apps (increasingly requested by users).

The ExpandingCollection repository is primarily a UI library with a demo application. The security posture is reasonable for a display-focused library, but there are gaps in dependency management, security policies, and explicit security configurations. No critical vulnerabilities were identified, but the lack of a Package.swift or dependency management file prevents proper vulnerability tracking. The codebase would benefit from a formal security policy, explicit dependency management, and documentation of secure coding practices. No evidence of hardcoded secrets, injection vulnerabilities, or infrastructure misconfigurations was found.

• Medium · No Dependency Management File Found — Repository root. The repository lacks a Package.swift, Podfile, Cartfile, or package management configuration file. This makes it impossible to track dependencies, versions, and potential security vulnerabilities in third-party libraries. Without explicit dependency management, there's no way to ensure reproducible builds or identify outdated packages. Fix: Implement Swift Package Manager (SPM) with a Package.swift file, CocoaPods with a Podfile, or Carthage with a Cartfile. Regularly audit and update dependencies using tools like swift package update or pod outdated.
• Low · Potential Hardcoded Configuration in Storyboards — DemoExpandingCollection/Base.lproj/Main.storyboard, DemoExpandingCollection/Base.lproj/LaunchScreen.storyboard. The codebase uses storyboards (Main.storyboard, LaunchScreen.storyboard) for UI configuration. While not a direct security vulnerability, hardcoding UI logic or endpoints in storyboards can make it difficult to manage configuration changes and may inadvertently expose sensitive information if storyboards are not properly managed. Fix: Move sensitive configuration to configuration files or environment variables. Use programmatic UI construction or externalize storyboard data where possible. Ensure storyboards do not contain hardcoded API endpoints or credentials.
• Low · Missing Code Signing Configuration Details — DemoExpandingCollection/DemoExpandingCollection.xcodeproj/project.pbxproj. The Xcode project configuration file (project.pbxproj) is present but without visibility into its contents, it's unclear if proper code signing and provisioning profiles are configured. This could lead to unsigned or improperly signed builds. Fix: Ensure code signing is properly configured with valid provisioning profiles and certificates. Use Xcode's automatic code signing feature or explicitly manage signing identities. Store certificates securely and never commit them to version control.
• Low · No Security Policy or SECURITY.md File — Repository root. The repository does not contain a SECURITY.md file or security policy, making it unclear how security vulnerabilities should be reported. This can lead to security issues being disclosed publicly rather than responsibly. Fix: Create a SECURITY.md file that outlines the vulnerability disclosure policy, including how to report security issues responsibly (e.g., security@ramotion.com or a security advisory process).
• Low · Swift Version Not Explicitly Defined in Project — .swift-version, DemoExpandingCollection/DemoExpandingCollection.xcodeproj/project.pbxproj. While a .swift-version file exists, the Swift version compatibility and minimum deployment target may not be clearly enforced across the build configuration. Using outdated Swift versions may include known security vulnerabilities. Fix: Ensure the .swift-version file specifies a recent, supported Swift version. Define minimum iOS deployment target appropriately in Xcode build settings. Regularly update to the latest stable Swift version to receive security patches.
• Low · No Input Validation Framework Visible — DemoExpandingCollection/ViewControllers/, DemoExpandingCollection/Helpers/. Based on the file structure, there's no evidence of centralized input validation or sanitization utilities. View controllers and helper classes should implement proper input validation to prevent unexpected behavior or crashes. Fix: Implement input validation and sanitization for all user inputs and data received from external sources. Create a centralized validation utility module and apply it consistently across the application.

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.