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/romandanylyk/PageIndicatorView 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.

AVOID — Stale and unlicensed — last commit 2y ago

• 8 active contributors
• ⚠ Stale — last commit 2y ago
• ⚠ Single-maintainer risk — top contributor 91% of recent commits
• ⚠ No license — legally unclear to depend on
• ⚠ 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 romandanylyk/PageIndicatorView repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/romandanylyk/PageIndicatorView.

What it runs against: a local clone of romandanylyk/PageIndicatorView — 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 romandanylyk/PageIndicatorView | Confirms the artifact applies here, not a fork | | 2 | Default branch master exists | Catches branch renames | | 3 | 5 critical file paths still exist | Catches refactors that moved load-bearing code | | 4 | Last commit ≤ 667 days ago | Catches sudden abandonment since generation |

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

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

# 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 "pageindicatorview/src/main/java/com/rd/PageIndicatorView.java" \\
  && ok "pageindicatorview/src/main/java/com/rd/PageIndicatorView.java" \\
  || miss "missing critical file: pageindicatorview/src/main/java/com/rd/PageIndicatorView.java"
test -f "pageindicatorview/src/main/java/com/rd/IndicatorManager.java" \\
  && ok "pageindicatorview/src/main/java/com/rd/IndicatorManager.java" \\
  || miss "missing critical file: pageindicatorview/src/main/java/com/rd/IndicatorManager.java"
test -f "pageindicatorview/src/main/java/com/rd/animation/AnimationManager.java" \\
  && ok "pageindicatorview/src/main/java/com/rd/animation/AnimationManager.java" \\
  || miss "missing critical file: pageindicatorview/src/main/java/com/rd/animation/AnimationManager.java"
test -f "pageindicatorview/src/main/java/com/rd/draw/DrawManager.java" \\
  && ok "pageindicatorview/src/main/java/com/rd/draw/DrawManager.java" \\
  || miss "missing critical file: pageindicatorview/src/main/java/com/rd/draw/DrawManager.java"
test -f "pageindicatorview/src/main/java/com/rd/draw/data/Indicator.java" \\
  && ok "pageindicatorview/src/main/java/com/rd/draw/data/Indicator.java" \\
  || miss "missing critical file: pageindicatorview/src/main/java/com/rd/draw/data/Indicator.java"

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

PageIndicatorView is a lightweight Android library that renders animated page indicator dots for ViewPager navigation with 8+ animation styles (worm, slide, fill, drop, scale, color, swap, thin_worm). It replaces the default static dot indicators with smooth, customizable animations that respond to ViewPager page transitions. Single-module library structure: core logic in pageindicatorview/src/main/java/com/rd/ split into 4 layers — PageIndicatorView.java (entry point), IndicatorManager.java (orchestrator), animation/AnimationManager.java (transition control), and animation/type/.java + animation/data/type/.java (8 concrete animation implementations). Each animation type has both a controller class (BaseAnimation subclass) and a data model class (AnimationValue subclass).

Android developers building apps with ViewPager (or similar paged content) who want polished, animated indicators without writing custom drawing code. Commonly used in onboarding screens, image galleries, and tab-based navigation UIs.

Moderately mature and stable. The codebase is feature-complete with 8 distinct animation types, extensive customization attributes (piv_animationType, piv_dynamicCount, piv_interactiveAnim visible in README), and published on Bintray/jcenter. However, based on the file structure showing no test directory visible and Gradle plugin versions from 2018 (gradle:3.2.1, bintray-gradle-plugin:1.7.3), active maintenance appears dormant but the core library is production-ready.

Low to moderate risk. Single-maintainer (romandanylyk) with no visible CI/CD setup in provided files and outdated Gradle toolchain (Android Gradle Plugin 3.2.1 from 2018). The appcompat-v7 dependency is deprecated in favor of AndroidX. No visible test suite in file listing increases regression risk when updating. Dependency count is low (appcompat, recyclerview, support-core-ui), mitigating supply chain risk.

No visible active development in provided data. The repository appears stable/archived with no pending PRs or milestones mentioned. The codebase is feature-frozen at ~140KB of Java code across 9 animation types and full XML attribute customization.

git clone https://github.com/romandanylyk/PageIndicatorView.git
cd PageIndicatorView
./gradlew build

The project uses Gradle wrapper (gradlew/gradlew.bat); no npm or additional package manager needed.

Daily commands: This is a library, not an executable app. To test locally: ./gradlew pageindicatorview:assembleDebug builds the AAR. Integration: add implementation project(':pageindicatorview') to a test app's build.gradle, then instantiate PageIndicatorView in an Activity and call setCount() and setSelection().

• pageindicatorview/src/main/java/com/rd/PageIndicatorView.java — Main public API entry point; all contributors must understand how this view exposes lifecycle, attributes, and pager integration
• pageindicatorview/src/main/java/com/rd/IndicatorManager.java — Orchestrates the entire indicator system (drawing, animation, state); core coordinator that must be understood before modifying behavior
• pageindicatorview/src/main/java/com/rd/animation/AnimationManager.java — Manages all animation types and transitions; essential for adding or modifying animations
• pageindicatorview/src/main/java/com/rd/draw/DrawManager.java — Manages drawing pipeline and delegates to specific drawers; understand this before changing visual output
• pageindicatorview/src/main/java/com/rd/draw/data/Indicator.java — Core data model holding indicator state (count, position, colors, sizes); all animation and draw logic depends on this
• pageindicatorview/src/main/res/values/attrs.xml — XML attribute definitions; defines the public configuration surface and must be updated when adding new customizable properties
• pageindicatorview/src/main/java/com/rd/animation/type/AnimationType.java — Enum defining all supported animation types; must reference this when implementing new animations

Add a new animation type

1. Add new enum constant to AnimationType in pageindicatorview/src/main/java/com/rd/animation/type/AnimationType.java (pageindicatorview/src/main/java/com/rd/animation/type/AnimationType.java)
2. Create new AnimationValue subclass in pageindicatorview/src/main/java/com/rd/animation/data/type/ (e.g., MyCustomAnimationValue.java) (pageindicatorview/src/main/java/com/rd/animation/data/type/)
3. Create new BaseAnimation subclass in pageindicatorview/src/main/java/com/rd/animation/type/ (e.g., MyCustomAnimation.java) implementing onPageScrolled() (pageindicatorview/src/main/java/com/rd/animation/type/)
4. Register new animation in AnimationManager.createAnimation() switch statement (pageindicatorview/src/main/java/com/rd/animation/AnimationManager.java)
5. Create corresponding BaseDrawer subclass in pageindicatorview/src/main/java/com/rd/draw/drawer/type/ (e.g., MyCustomDrawer.java) (pageindicatorview/src/main/java/com/rd/draw/drawer/type/)
6. Register new drawer in DrawManager.createDrawer() switch statement (pageindicatorview/src/main/java/com/rd/draw/DrawManager.java)

Add a new XML attribute for customization

1. Define attribute in pageindicatorview/src/main/res/values/attrs.xml under the <declare-styleable name="PageIndicatorView"> block (pageindicatorview/src/main/res/values/attrs.xml)
2. Add field to Indicator data model in pageindicatorview/src/main/java/com/rd/draw/data/Indicator.java (pageindicatorview/src/main/java/com/rd/draw/data/Indicator.java)
3. Parse attribute in AttributeController.obtainAttributes() method (pageindicatorview/src/main/java/com/rd/draw/controller/AttributeController.java)
4. Add public setter method in PageIndicatorView.java to allow programmatic configuration (pageindicatorview/src/main/java/com/rd/PageIndicatorView.java)
5. Use the new attribute value in DrawManager or AnimationManager as needed (pageindicatorview/src/main/java/com/rd/draw/DrawManager.java)

Fix a drawing or animation bug

1. Identify the animation type from AnimationType enum (pageindicatorview/src/main/java/com/rd/animation/type/AnimationType.java)
2. Locate the corresponding animation class (e.g., WormAnimation) and examine onPageScrolled() logic (pageindicatorview/src/main/java/com/rd/animation/type/)
3. Verify the AnimationValue updates (e.g., WormAnimationValue) are correct (pageindicatorview/src/main/java/com/rd/animation/data/type/)
4. Check corresponding drawer (e.g., WormDrawer) for canvas drawing issues (pageindicatorview/src/main/java/com/rd/draw/drawer/type/)
5. Test fix by building sample app and verifying in HomeActivity or CustomizeActivity (sample/src/main/java/com/rd/pageindicatorview/home/HomeActivity.java)

• Custom Android View (Canvas drawing) — Lightweight, high-performance rendering of simple geometric shapes without RecyclerView or complex hierarchy overhead
• Strategy pattern (Animation types, Drawers) — Allows pluggable animation and drawing implementations; easy to add new types without modifying core logic
• Data-driven architecture (Indicator model) — Separates state from rendering; animation and drawing logic consume the same Indicator model, ensuring consistency
• ViewPager integration (OnPageChangeListener) — Tight coupling with ViewPager is intentional; allows smooth animation driven by user scroll gestures in real-time

• Separate Animation and Drawer classes for each animation type

  • Why: Provides clear separation of concerns and allows independent testing/modification of animation logic vs. rendering
  • Consequence: More files and boilerplate; adding new animation requires changes in multiple places (AnimationType enum, AnimationManager, DrawManager, data/type folder)

• No built-in state persistence beyond PositionSavedState

  • Why: Assumes host Activity/Fragment manages ViewPager state; simplifies library scope
  • Consequence: Parent is responsible for saving/restoring page position across configuration changes

• Direct Canvas drawing instead of composable UI

  • Why: undefined
  • Consequence: undefined

AndroidX migration: The library targets appcompat-v7 v27.1.1 (2018), which is deprecated in favor of androidx.*; projects already migrated to AndroidX may face version conflicts. ViewPager 1 only: No evidence of ViewPager2 support in file names or README snippet; apps using ViewPager2 will need custom integration. No JUnit tests visible: Behavior is only testable via manual instrumentation on a real Android device or emulator. Gradle wrapper pin: Uses gradle-wrapper.properties with a hardcoded old Gradle version; must manually update to build with AGP 4.0+.

• ValueAnimator frame interpolation — PageIndicatorView drives all 8 animation types via ValueAnimator callbacks; understanding interpolation curves (linear, accelerate, decelerate) is essential to modifying or adding animations
• ViewPager.OnPageChangeListener — IndicatorManager wires indicator state changes to ViewPager scroll/selection events; must understand the three callback methods (onPageScrolled, onPageSelected, onPageScrollStateChanged) to integrate with custom ViewPager subclasses
• Android Canvas drawing and Path composition — The animation types (Worm, Slide, Drop) use Path and Canvas.drawPath() to morph indicator shapes on each frame; visual bugs require low-level drawing debugging
• Strategy pattern for animation polymorphism — Each animation type (WormAnimation, SlideAnimation, etc.) is a BaseAnimation subclass; understanding this pattern is key to adding new animation types without modifying AnimationManager
• XML attribute parsing and TypedArray — PageIndicatorView.java uses TypedArray to read piv_* attributes from XML layouts; customization depends on correctly parsing and caching these attributes
• Android data binding and measure/layout cycles — Indicators must respond to parent container resizing and density changes; View.onMeasure() and onLayout() logic affects indicator positioning and animation bounds

• dotsindicator/dots-indicator — Modern AndroidX-compatible page indicator with animation support; actively maintained alternative using ViewPager2
• lsjwzh/CircleIndicator — Simpler ViewPager indicator without animations; lighter-weight alternative for use cases not requiring motion effects
• android/architecture-samples — Google's canonical Android project templates; useful for seeing modern Gradle configs and testing patterns to backport into PageIndicatorView
• ReactiveX/RxAndroid — Common dependency in modern Android libraries; relevant if PageIndicatorView adoption grows to include RxJava-based ViewPager2 adapters

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 unit tests for animation value classes (AnimationValue.java and type subclasses)

The animation system has 8 different AnimationValue implementations (ColorAnimationValue, DropAnimationValue, FillAnimationValue, etc.) in pageindicatorview/src/main/java/com/rd/animation/data/type/ but there are no visible test files. These classes handle critical animation calculations and should have unit test coverage to prevent regressions when modifying animation behavior.

• [ ] Create pageindicatorview/src/test/java/com/rd/animation/data/type/ directory structure
• [ ] Add unit tests for each AnimationValue subclass covering value interpolation and boundary conditions
• [ ] Add tests for AnimationManager.java to verify animation sequencing and state transitions
• [ ] Ensure tests cover both normal and edge cases (e.g., page count of 1, rapid page changes)

Add GitHub Actions CI/CD workflow for automated testing and publishing

The repo uses Bintray for publishing (gradle-bintray-plugin in build.gradle) but lacks a .github/workflows/ directory for automated testing, linting, and release builds. This prevents catching build failures early and makes releases manual and error-prone. A workflow would validate PRs before merge and automate publishing to Maven/Bintray.

• [ ] Create .github/workflows/android-ci.yml to run gradlew build and test on PR/push to main branches
• [ ] Add Android lint checking to catch API compatibility issues (minimum API 14)
• [ ] Add workflow for automated publishing to Bintray on version tag creation (v*.. tags)
• [ ] Document the CI setup in README.md with badge showing build status

Add comprehensive JavaDoc documentation to public API classes (PageIndicatorView.java, AnimationType.java, Indicator.java)

The main public API classes lack JavaDoc comments, making it harder for contributors and library users to understand the behavior and expected usage. PageIndicatorView.java is the entry point, AnimationType.java defines available animation types, and Indicator.java holds configuration data - these need clear documentation of methods, parameters, and usage examples.

• [ ] Add class-level JavaDoc to PageIndicatorView.java explaining purpose, lifecycle, and usage with ViewPager
• [ ] Document all public methods in PageIndicatorView.java with @param, @return, and usage examples
• [ ] Add JavaDoc to AnimationType enum explaining each animation type and when to use it
• [ ] Document Indicator.java data class fields and builder pattern if applicable
• [ ] Add links to relevant animation GIFs from assets/ folder in method documentation

• Add unit tests for ValueController interpolation logic in pageindicatorview/src/main/java/com/rd/animation/controller/ValueController.java — currently untested and critical for animation smoothness. Start with frame-by-frame interpolation bounds checks.
• Implement ViewPager2 adapter support in IndicatorManager.java; currently only ViewPager (androidx.viewpager:viewpager v1) is supported, but ViewPager2 is the new standard since AndroidX. Requires wrapping PagerChangeCallback instead of OnPageChangeListener.
• Add XML attribute documentation in the README for all piv_* attributes visible in code (piv_animationType, piv_dynamicCount, piv_interactiveAnim, etc.); README snippet shows partial usage but lacks a full reference table of defaults and valid values.

This codebase has critical security vulnerabilities stemming from severely outdated build infrastructure. The Gradle plugins (3.2

• High · Outdated Gradle Build Plugin — build.gradle (classpath 'com.android.tools.build:gradle:3.2.1'). The project uses Android Gradle plugin version 3.2.1, released in September 2018. This version is significantly outdated and contains known security vulnerabilities. Modern Android development requires at least Gradle 7.x with Android Gradle plugin 7.x or higher for security patches and vulnerability fixes. Fix: Update to the latest stable Android Gradle plugin version (currently 8.x). Use 'com.android.tools.build:gradle:8.1.0' or later.
• High · Outdated Bintray Gradle Plugin — build.gradle (classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.7.3'). The gradle-bintray-plugin version 1.7.3 is outdated (released in 2017). Bintray was acquired by JFrog and eventually shut down. This plugin is no longer maintained and may contain unpatched security vulnerabilities. Additionally, Bintray's repository no longer exists, potentially causing dependency resolution failures. Fix: Migrate to JFrog Artifactory or Maven Central publishing. If using Maven Central, use the gradle-maven-publish-plugin or native Maven publishing instead of the deprecated Bintray plugin.
• High · Outdated Android Maven Gradle Plugin — build.gradle (classpath 'com.github.dcendents:android-maven-gradle-plugin:1.5'). The android-maven-gradle-plugin version 1.5 is deprecated and no longer maintained (last updated around 2015). This plugin may contain unpatched security vulnerabilities and is incompatible with modern Gradle versions. Fix: Replace with the official gradle-maven-publish-plugin or Maven Central's publishing mechanisms. Use 'com.vanniktech:gradle-maven-publish-plugin:0.25.3' or later as a modern alternative.
• Medium · Insecure Repository Configuration — build.gradle (repositories section). The build.gradle uses jcenter() repository which was deprecated and shut down by JFrog in 2021. Depending on this repository may fail or serve outdated/compromised artifacts. Only google() and mavenCentral() should be used. Fix: Replace jcenter() with mavenCentral(). Update both buildscript and allprojects repositories to use only google() and mavenCentral().
• Medium · Missing Dependency Version Constraints — build.gradle (pageindicatorview module). The build.gradle file does not appear to specify compileSdkVersion, targetSdkVersion, or minSdkVersion constraints explicitly in the visible configuration. The README mentions API 14+ support, which is extremely outdated (Android 4.0, released 2011). Modern Android requires API 23+ minimum. Fix: Set targetSdkVersion and compileSdkVersion to at least 33 (Android 13). Update minSdkVersion to at least 21 (Android 5.0) for better security and feature support.
• Low · ProGuard Rules Not Visible — pageindicatorview/proguard-rules.pro and sample/proguard-rules.pro. While proguard-rules.pro files exist, their content is not provided for analysis. ProGuard misconfiguration could expose sensitive class names or methods, or overly aggressive rules could introduce runtime issues. Fix: Review ProGuard/R8 rules to ensure: (1) sensitive classes are properly obfuscated, (2) necessary classes are kept (e.g., callback interfaces), (3) rules follow Android best practices.
• Low · No Explicit Security Provider Configuration — Project structure - no Security Provider initialization visible. The codebase does not show explicit initialization of security providers. While less critical for a UI library, proper cryptographic provider configuration is a security best practice if any network operations occur. Fix: If the library performs any HTTPS communications, explicitly initialize security providers using SecurityProviderInstaller from AndroidX Security library.

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.