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/florent37/MaterialViewPager 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.

GO — Healthy across all four use cases

• 20 active contributors
• Apache-2.0 licensed
• CI configured
• Tests present
• ⚠ Stale — last commit 8y ago
• ⚠ Concentrated ownership — top contributor handles 70% of recent commits

_{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 florent37/MaterialViewPager repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/florent37/MaterialViewPager.

What it runs against: a local clone of florent37/MaterialViewPager — 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 florent37/MaterialViewPager | Confirms the artifact applies here, not a fork | | 2 | License is still Apache-2.0 | 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 ≤ 2795 days ago | Catches sudden abandonment since generation |

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

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

# 2. License matches what RepoPilot saw
(grep -qiE "^(Apache-2\\.0)" LICENSE 2>/dev/null \\
   || grep -qiE "\"license\"\\s*:\\s*\"Apache-2\\.0\"" package.json 2>/dev/null) \\
  && ok "license is Apache-2.0" \\
  || miss "license drift — was Apache-2.0 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 "materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPager.java" \\
  && ok "materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPager.java" \\
  || miss "missing critical file: materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPager.java"
test -f "materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerAnimator.java" \\
  && ok "materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerAnimator.java" \\
  || miss "missing critical file: materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerAnimator.java"
test -f "materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerHelper.java" \\
  && ok "materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerHelper.java" \\
  || miss "missing critical file: materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerHelper.java"
test -f "materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerHeaderView.java" \\
  && ok "materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerHeaderView.java" \\
  || miss "missing critical file: materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerHeaderView.java"
test -f "materialviewpager/src/main/res/layout/material_view_pager_layout.xml" \\
  && ok "materialviewpager/src/main/res/layout/material_view_pager_layout.xml" \\
  || miss "missing critical file: materialviewpager/src/main/res/layout/material_view_pager_layout.xml"

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

MaterialViewPager is an Android library that implements a Material Design-compliant ViewPager with a collapsible parallax header, animated title strips, and synchronized toolbar behavior. It provides a ready-to-use component (MaterialViewPager) that handles the complex interaction between page scrolling, header collapse/expansion, and toolbar visibility without boilerplate, commonly seen in Google Play and Gmail-style interfaces. Single-module library structure: materialviewpager/src/main/java/com/github/florent37/materialviewpager/ contains core classes (MaterialViewPager.java, MaterialViewPagerAnimator.java, MaterialViewPagerHelper.java) with a dedicated header/ package for header variants (image, Ken Burns, decorator). Layout XMLs in res/layout/ define the template structure; Gradle config in build.gradle and gradle/bintray-android-v1.gradle handles publishing.

Android developers building Material Design apps who need a polished ViewPager with parallax headers and toolbar integration without implementing complex scroll-sync animations from scratch. Particularly useful for product detail screens, news feeds, and multi-tab layouts.

Moderately mature but aging: version 1.2.3 is stable and published to Bintray/JCenter, with CI/CD via CircleCI and active Android Arsenal/Weekly recognition. However, the repo targets minSdk=14 and buildTools=26.0.2 (Android 8.0), suggesting last meaningful updates around 2017-2018; no visible recent commits or test suite in the file listing raises concerns about maintenance.

Moderate risk: depends on legacy libraries (KenBurnsView 1.0.7, MaterialTabStrip 1.1.0, Glide 4.0.0) without pinned versions in some cases, and the single maintainer (florent37) shows no visible activity indicators. The codebase is Java-only with minSdk=14 compatibility requirements, making it incompatible with modern Gradle versions; no test coverage visible suggests refactoring risk.

No active development visible in provided file listing; the repo appears dormant. Version 1.2.3 is the latest, and there are no visible open PRs, recent commits, or issue milestones mentioned in the data.

Clone and build with Gradle:

git clone https://github.com/florent37/MaterialViewPager.git
cd MaterialViewPager
./gradlew build

Or add to your project's build.gradle:

compile 'com.github.florent37:materialviewpager:1.2.3'
compile 'com.flaviofaria:kenburnsview:1.0.7'
compile 'com.jpardogo.materialtabstrip:library:1.1.0'
compile 'com.github.bumptech.glide:glide:4.0.0'

Daily commands: No runnable server; this is a library. To test locally, import into Android Studio (Gradle sync occurs automatically). Use ./gradlew assembleDebug to build the .aar, or reference it in a sample app's build.gradle. CircleCI is configured in circle.yml for automated builds.

• materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPager.java — Core entry point and main orchestrator for the entire ViewPager system; all integration starts here.
• materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerAnimator.java — Handles all scroll and parallax animations; critical to Material Design visual behavior.
• materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerHelper.java — Configuration and setup helper; necessary for initializing the library in activities.
• materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerHeaderView.java — Header view wrapper; manages the collapsible/parallax header that is core to the design pattern.
• materialviewpager/src/main/res/layout/material_view_pager_layout.xml — Main layout structure defining the ViewPager with header and content sections.
• materialviewpager/src/main/res/values/attrs.xml — Custom attributes for XML configuration; required for customizing library behavior in layouts.

Add a Custom Header Design

1. Create a new header class extending HeaderDesign (materialviewpager/src/main/java/com/github/florent37/materialviewpager/header/HeaderDesign.java)
2. Implement header layout XML in res/layout/ (materialviewpager/src/main/res/layout/)
3. Register and configure in MaterialViewPagerHelper.setup() (materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerHelper.java)

Integrate ViewPager into an Activity

1. Add MaterialViewPager to your activity layout (sample/src/main/res/layout/activity_main.xml)
2. Call MaterialViewPagerHelper.setup() in onCreate() (sample/src/main/java/com/github/florent37/materialviewpager/sample/MainActivity.java)
3. Configure header via setMaterialViewPagerHeader() method (materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPager.java)

Add Fragment Content with RecyclerView

1. Create fragment with RecyclerView layout (sample/src/main/res/layout/fragment_recyclerview.xml)
2. Extend RecyclerViewFragment and implement adapter (sample/src/main/java/com/github/florent37/materialviewpager/sample/fragment/RecyclerViewFragment.java)
3. Register listener with MaterialViewPagerAnimator for scroll events (materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerAnimator.java)

Customize Animation & Parallax Behavior

1. Access MaterialViewPagerAnimator from MaterialViewPager (materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPager.java)
2. Adjust parallax multiplier and animation parameters (materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerSettings.java)
3. Override animation logic in MaterialViewPagerAnimator (materialviewpager/src/main/java/com/github/florent37/materialviewpager/MaterialViewPagerAnimator.java)

• Android ViewPager — Standard Android component for horizontal swiping between fragments; core to Material Design tab navigation patterns.
• Custom View Subclasses (MaterialViewPager, MaterialViewPagerHeaderView) — Enables fine-grained control over parallax scrolling, header collapse, and animation timing at the view layer.
• Scroll Listeners & Animators — Required to detect content scroll and apply real-time parallax transformations to headers without frame drops.
• Android Support Library (AppCompat, Design) — Provides Material Design components and backwards compatibility for older API levels.

• Parallax header implemented via scroll listener instead of MotionLayout

  • Why: Library predates MotionLayout (Android 3.4); direct animation gives more granular control over timing and easing.
  • Consequence: More boilerplate code in MaterialViewPagerAnimator; harder to preview in layout editor; but fully compatible with older Android versions.

• Separate header and content layers rather than unified scrolling

  • Why: Allows independent parallax scaling and collapse without complex nested scroll behavior.
  • Consequence: Requires manual sync between header and content scroll positions; can cause jank if listener callback is slow.

• Fragment-based content model

  • Why: Natural fit for ViewPager; encourages modular, reusable page designs.
  • Consequence: Fragment lifecycle overhead; state restoration complexity; not suitable for very high-frequency updates.

• Does not provide built-in authentication or login flows.
• Does not handle real-time data synchronization.
• Does not include networking or HTTP client (caller must integrate OkHttp, Retrofit, etc.).
• Not a form builder or data validation framework.
• Does not provide backend API or server functionality.

No unit tests visible in file listing—testing requires manual Android device/emulator verification. BuildTools 26.0.2 and Gradle 3.0.1 are outdated; you may encounter deprecation warnings or incompatibilities with modern Android Studio. The library uses old Glide 4.0.0 syntax (not AndroidX); mixing with AndroidX projects requires careful dependency management. No ProGuard configuration visible beyond proguard-rules.pro; if used with minification, ensure reflection-based code is preserved. Ken Burns View dependency has no active maintenance.

• ViewPager scroll event synchronization — This library's core mechanic: scroll events from the ViewPager drive parallax animations and toolbar state; understanding scroll listener chains and timing is essential to modifying animation behavior.
• Parallax scrolling — The header moves at a different rate than page content (e.g., 1.5x slower) to create depth; parallaxHeaderFactor attribute controls this ratio.
• Nested scroll interception — MaterialViewPagerHelper.java intercepts nested RecyclerView/ListView scroll events to sync them with header collapse; critical for pages containing scrollable lists.
• Translational animation — Header and toolbar animate via Y-axis translation based on scroll offset; MaterialViewPagerAnimator.java calculates translation values frame-by-frame.
• Toolbar elevation (Material Design) — The library can dynamically toggle toolbar elevation/shadow based on scroll state; controlled by enableToolbarElevation attribute to match Material Design specs.

• chrisbanes/cheesesquare — Official Material Design pattern reference for collapsible toolbars and parallax headers; influenced this library's design.
• saket/inboxrecyclerview — Modern alternative for collapsible header + list scroll behavior using CoordinatorLayout and AppBarLayout (post-Material Design support library).
• gturk/flipboard-like-view-pager — Similar ViewPager variant with custom scroll-driven animations; good reference for scroll event handling patterns.
• flaviofaria/KenBurnsView — Direct dependency of this library; provides the animated parallax header effect when used with image headers.
• bumptech/glide — Image loading library used by example headers; integrates with MaterialViewPagerImageHelper.java for efficient image handling.

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 instrumented Android unit tests for MaterialViewPagerAnimator.java

The MaterialViewPagerAnimator.java class handles critical animation logic for the library but has no corresponding test file. Adding instrumented tests would validate scroll behavior, header animations, and parallax effects across different API levels. This is essential for a Material Design animation library.

• [ ] Create materialviewpager/src/androidTest/java/com/github/florent37/materialviewpager/MaterialViewPagerAnimatorTest.java
• [ ] Write tests for scroll offset calculations and animation state transitions
• [ ] Test header translation and alpha animation values at different scroll positions
• [ ] Run tests against minSdk=14 and sdk=27 to ensure backward compatibility

Add GitHub Actions CI workflow to replace CircleCI (migrate from circle.yml)

The repo uses CircleCI (circle.yml exists) but modern Android projects typically use GitHub Actions for better GitHub integration. A GitHub Actions workflow would provide faster feedback, better PR integration, and no need for external CI service configuration.

• [ ] Create .github/workflows/android-ci.yml with Android Gradle build, lint, and test tasks
• [ ] Configure the workflow to run on push and pull_request events
• [ ] Include build steps for both materialviewpager library module and sample app
• [ ] Add Gradle caching to speed up builds (reference gradle-wrapper.properties for Gradle version)

Create comprehensive documentation for MaterialViewPagerSettings.java configuration options

MaterialViewPagerSettings.java contains configuration logic but README.md lacks detailed setup documentation with actual code examples. New contributors cannot easily understand how to configure header designs, parallax settings, or custom animations.

• [ ] Create docs/CONFIGURATION.md documenting all MaterialViewPagerSettings properties
• [ ] Add code examples showing configuration for MaterialViewPagerImageHeader and MaterialViewPagerKenBurnsHeader
• [ ] Document the relationship between HeaderDesign.java enum and MaterialViewPagerHeaderDecorator.java
• [ ] Include troubleshooting section for common issues like header not animating (reference MaterialViewPagerHelper.java)

• Add unit test coverage for MaterialViewPagerAnimator.java scroll event handling—currently untestable without manual emulator runs; create a JUnit test suite using mock ViewPager scroll events.: No test suite visible; animaton logic is critical and error-prone.
• Document the nested RecyclerView integration pattern in README with a concrete code example—MaterialViewPagerHelper.java exists but its role is unexplained, causing confusion when nesting lists inside pages.: README lacks detail on common use case; many developers struggle with nested scroll behavior.
• Modernize dependencies: upgrade Glide to 4.11+, MaterialTabStrip to 1.2+, and bump minSdk to 21; update Gradle to 4.x+ and Android Plugin to 3.5+—codebase is Android 8.0 era.: Current stack is ~5 years old; blocks adoption by developers using modern Android Studio and AndroidX.

The MaterialViewPager project has several security concerns, primarily related to outdated dependencies and insecure repository configurations. The most critical issues are: (1) use of HTTP instead of HTTPS for Maven repositories, (2) significantly outdated Gradle and build tools (from ~2017), (3) deprecated Fabric plugin, and (4) dynamic version specifiers allowing unpredictable updates. The minimum SDK version of 14 is also far below modern standards. These issues should

• High · Insecure HTTP Repository — build.gradle (buildscript repositories section). The build.gradle file contains an insecure HTTP Maven repository (http://dl.bintray.com/jfrog/jfrog-jars) without HTTPS encryption. This allows potential man-in-the-middle attacks where dependencies could be intercepted and replaced with malicious versions. Fix: Replace all HTTP repositories with HTTPS equivalents. Change 'http://dl.bintray.com/jfrog/jfrog-jars' to 'https://dl.bintray.com/jfrog/jfrog-jars'
• Medium · Outdated Gradle Plugin Version — build.gradle (classpath 'com.android.tools.build:gradle:3.0.1'). The build uses Gradle 3.0.1 (classpath 'com.android.tools.build:gradle:3.0.1') which is significantly outdated and likely contains known security vulnerabilities. Current Android Gradle Plugin versions are 7.x and 8.x. Fix: Update to the latest stable Android Gradle Plugin version (8.0.0 or later). Review and update all other build tool dependencies to current versions.
• Medium · Unversioned Gradle Plugin Dependency — build.gradle (classpath 'com.github.ben-manes:gradle-versions-plugin:+' and classpath 'io.fabric.tools:gradle:1.+'). The gradle-versions-plugin dependency uses a dynamic version specifier ('+') which can pull in breaking changes. Additionally, the Fabric gradle plugin uses '1.+' which is also dynamic and unpredictable. Fix: Replace dynamic version specifiers with specific pinned versions. Use explicit version numbers like '0.50.0' instead of '+' or '1.+'.
• Medium · Deprecated Fabric Plugin Dependency — build.gradle (classpath 'io.fabric.tools:gradle:1.+'). The Fabric plugin (io.fabric.tools:gradle) has been deprecated and is no longer maintained. It should be replaced with Firebase Crashlytics. This may contain unpatched vulnerabilities. Fix: Migrate from Fabric to Firebase Crashlytics. Update dependencies and remove the deprecated Fabric plugin.
• Low · Insecure Bintray Repository (HTTP) — build.gradle (allprojects repositories section). Custom Bintray repository URL uses HTTP instead of HTTPS (maven { url "http://dl.bintray.com/florent37/maven" }). While Bintray is now deprecated in favor of JCenter/Maven Central, any remaining HTTP repositories should use HTTPS. Fix: Use HTTPS for all repository URLs. Consider migrating dependencies from Bintray to Maven Central or JCenter.
• Low · Min SDK Version Below Current Standard — build.gradle (ext { minSdk = 14 }). The minSdk is set to 14, which is an Android version from 2013 (Ice Cream Sandwich). Google Play now requires minSdk of 24+ for new apps. Supporting very old Android versions increases attack surface. Fix: Increase minSdk to at least 24 (Android 7.0) to align with modern security standards and Google Play requirements. Support only recent Android versions.
• Low · Gradle Wrapper JAR Not Verified — gradle/wrapper/gradle-wrapper.jar. The gradle-wrapper.jar file is committed to version control. While this isn't a vulnerability per se, if the jar is compromised, it could lead to supply chain attacks. The gradle wrapper should ideally be verified. Fix: Add gradle-wrapper.jar to .gitignore and require developers to use verified distribution. Consider using Gradle verification metadata for wrapper checksums.

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.