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/JakeWharton/ViewPagerIndicator 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 8y ago

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

What it runs against: a local clone of JakeWharton/ViewPagerIndicator — 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 JakeWharton/ViewPagerIndicator | Confirms the artifact applies here, not a fork | | 2 | Default branch master exists | Catches branch renames | | 3 | Last commit ≤ 3115 days ago | Catches sudden abandonment since generation |

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

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

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

ViewPagerIndicator provides pluggable paging indicator widgets (CirclePageIndicator, TitlePageIndicator, TabPageIndicator, LinePageIndicator, UnderlinePageIndicator, IconPageIndicator) that visually represent the current page position in Android's ViewPager from the Support Library. It solves the problem of displaying intuitive page navigation UI without building custom indicators from scratch. Simple library structure: library/src/com/viewpagerindicator/ contains 7 indicator widget implementations (CirclePageIndicator.java, TitlePageIndicator.java, etc.) all implementing the PageIndicator interface. Resources live in library/res/ (drawables, colors, styles). A sample/ folder provides a working reference app. Maven multi-module project (parent pom.xml + library/pom.xml) with Android Maven Plugin build.

Android app developers building tabbed or paginated UIs who need out-of-the-box indicator widgets compatible with Android Support Library's ViewPager and ActionBarSherlock. Particularly useful for teams that want styled, themeable indicators without writing custom View code.

This is a stable, mature library (version 2.4.1 visible in pom.xml) with comprehensive resource assets (drawable-hdpi/mdpi/xhdpi nine-patch images) and documented styling APIs. However, there are no visible test files in the structure, and the last commit date is not provided—treat as production-ready but potentially unmaintained (common for pre-Material Design Android libraries). No active CI configuration visible in file list.

Single external dependency (android-support-v4.jar), which is stable but the library predates modern Android tooling (pom.xml and ant-based build, no Gradle config visible). Risks include: no test coverage visible, potential compatibility issues with modern Android SDK versions (minSdkVersion not shown), and single-maintainer maintenance burden (Jake Wharton, though he is no longer as active in Android ecosystem). The nine-patch drawable assets are version-locked and cannot scale to modern screen densities beyond xhdpi.

No active development signals visible in the provided file list. The project appears dormant post-2.4.1 release. No recent commits, PRs, or issues data provided—this is a maintenance-mode library.

git clone https://github.com/JakeWharton/ViewPagerIndicator.git && cd ViewPagerIndicator && mvn clean install (requires Maven 3.x and Android SDK). For Eclipse: Import as existing Android library project and reference in your app. See sample/ folder for working implementation.

Daily commands: This is a library, not a runnable app. To test: import into Android Studio/Eclipse, build with mvn clean install, or reference the sample app: cd sample && mvn clean install android:deploy android:run. The sample APK is the entry point for manual testing.

• library/src/com/viewpagerindicator/PageIndicator.java: Core interface that all 6 indicator implementations must satisfy—defines setViewPager(), setOnPageChangeListener(), onPageScrolled() contract
• library/src/com/viewpagerindicator/CirclePageIndicator.java: Most popular indicator widget—implements dot circle rendering logic, demonstrating the Canvas drawing pattern used across all indicators
• library/src/com/viewpagerindicator/TitlePageIndicator.java: Title-based indicator showing page text; demonstrates text rendering and ViewPager integration with title-providing adapters
• library/res/values/vpi__attrs.xml: Custom XML attributes (vpi_*) that allow indicators to be styled declaratively in layout XMLs—required for the library's no-code styling promise
• library/libs/android-support-v4.jar: Only external dependency—provides ViewPager class and compat classes; version pinned here rather than Maven central

Indicator widget implementations: edit library/src/com/viewpagerindicator/CirclePageIndicator.java (or other indicator type). Styling: modify library/res/values/vpi__attrs.xml for custom attributes, library/res/color/vpi__dark_theme.xml and vpi__light_theme.xml for themes. Drawables: update nine-patch PNGs in library/res/drawable-{hdpi,mdpi,xhdpi}/. Sample app UI: sample/res/layout/ (not shown but implied).

Nine-patch drawables in library/res/drawable-{hdpi,mdpi,xhdpi}/ define visual style but do NOT scale to xxhdpi/xxxhdpi (modern phones)—you must generate or provide custom drawables. The library expects ViewPager's PagerAdapter to implement either PagerAdapter.getPageTitle() (TitlePageIndicator) or IconPagerAdapter interface (IconPageIndicator)—incompatible adapters will cause nullPointerExceptions. Custom namespace attributes (e.g., app:vpi_* in layout XMLs) require the library's xmlns declaration and may conflict with other libraries using 'vpi' prefix. Maven artifact uses deprecated 'apklib' packaging—modern Gradle builds need workarounds.

• Nine-patch image (9.png) — All indicator drawables use nine-patch format (vpi__tab_selected_holo.9.png) to scale correctly across different screen widths while preserving corners—core to this library's visual system
• ViewPager.OnPageChangeListener — All 6 indicator types implement this interface to sync their visual state with ViewPager scroll/selection events—essential pattern for understanding how indicators stay in sync
• Custom View with Canvas drawing (onDraw) — CirclePageIndicator, LinePageIndicator, TitlePageIndicator use custom Canvas.drawCircle(), Canvas.drawLine(), Paint objects to render indicators from scratch—not using pre-built widgets
• Android custom namespace attributes (xmlns:app) — Indicators use custom XML attributes (vpi_* defined in vpi__attrs.xml) for declarative styling in layout XMLs without code—core UX of the library
• PagerAdapter.getPageTitle() — TitlePageIndicator relies on adapters implementing this method to fetch page titles for display—contracts between library and user adapters
• Theme overlay (android:theme in resources) — Library applies dark/light theme overlays via vpi__dark_theme.xml and vpi__light_theme.xml color resources—enables visual customization without code

• google/android-support-library — Provides ViewPager base class that all indicators in this repo hook into—required dependency
• JakeWharton/ActionBarSherlock — Companion library by same author; ViewPagerIndicator explicitly supports themed integration with ActionBarSherlock for pre-API 11 apps
• PagerSlidingTabStrip/PagerSlidingTabStrip — Modern alternative indicator library with sliding underline style—competitor that emerged after ViewPagerIndicator for material design era
• smartisanos/android-viewpager-indicator — Community fork adding modern features like RTL support and vector drawable compatibility—shows how ecosystem extended this library
• androidx/androidx — Modern replacement for android-support-v4 library; ViewPagerIndicator's dependencies are now subsumed into AndroidX (project needs migration)

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.

Migrate from legacy Android support-v4 JAR to AndroidX dependencies

The repo still uses the old android-support-v4.jar bundled in library/libs and sample/libs directories. This is outdated and incompatible with modern Android development. Migrating to AndroidX (androidx.viewpager:viewpager) would make the library usable in contemporary Android projects and reduce maintenance burden. This requires updating pom.xml, removing JAR files, and ensuring all imports are updated.

• [ ] Update library/pom.xml to replace com.google.android:support-v4 with androidx.viewpager:viewpager dependency
• [ ] Remove library/libs/android-support-v4.jar and sample/libs/android-support-v4.jar
• [ ] Update all imports in library/src/com/viewpagerindicator/*.java from android.support.v4.view to androidx.viewpager.widget
• [ ] Test against sample application to ensure ViewPager and PagerAdapter integration still works
• [ ] Update README.md with AndroidX migration note

Add unit tests for PageIndicator implementations

The repo lacks any visible test directory structure. The five indicator implementations (CirclePageIndicator, LinePageIndicator, TitlePageIndicator, TabPageIndicator, UnderlinePageIndicator) in library/src/com/viewpagerindicator/ have no corresponding unit tests. Adding tests would improve code reliability, catch regressions during refactoring, and provide examples for maintainability.

• [ ] Create library/src/test/java/com/viewpagerindicator/ directory structure
• [ ] Write unit tests for CirclePageIndicator focusing on onPageScrolled(), onPageSelected(), and drawing behavior
• [ ] Write unit tests for LinePageIndicator with similar coverage of core methods
• [ ] Add TitlePageIndicator tests covering text measurement and page binding via PageIndicator interface
• [ ] Update pom.xml to include junit and mockito dependencies with test scope

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

The repo uses Maven (pom.xml) but lacks automated build verification. Adding a GitHub Actions workflow would catch build failures early, verify Android SDK compatibility, run checkstyle validation, and test against multiple API levels. This is critical for a maintained open source library to ensure contributions don't break the build.

• [ ] Create .github/workflows/build.yml with steps to: setup JDK, install Android SDK, run 'mvn clean verify'
• [ ] Configure the workflow to run on push to main branches and all pull requests
• [ ] Add checkstyle validation step that runs maven-checkstyle-plugin against library/src/
• [ ] Include Android emulator tests or instrumentation test execution if sample tests exist
• [ ] Add workflow status badge to README.md pointing to GitHub Actions

• Add unit tests for CirclePageIndicator.onDraw() rendering logic—no test files exist in the structure. Start by creating library/test/com/viewpagerindicator/CirclePageIndicatorTest.java with Robolectric to verify circle positions and paint states.
• Generate xxhdpi and xxxhdpi nine-patch drawables (library/res/drawable-xxhdpi/ and drawable-xxxhdpi/) from existing xhdpi PNGs—modern devices need these DPI buckets. Use Android Asset Studio or manual scaling with 9patch tool.
• Document the PageIndicator interface contract with JavaDoc examples in library/src/com/viewpagerindicator/PageIndicator.java—currently undocumented. Add usage examples showing required ViewPager.PagerAdapter methods (getPageTitle, getCount) for each indicator type.

This Android library project has significant security concerns related to its age and use of deprecated dependencies. The primary issues are: (1) dependence on outdated android-support-v4 library instead of modern AndroidX, (2) use of obsolete build tools and packaging formats, (3) lack of explicit dependency version management, and (4) no explicit HTTPS configuration for dependency repositories. The project has not been modernized to current Android development standards and security best practices. Immediate action is recommended to update the build system to Gradle, migrate to AndroidX, and pin all dependency versions explicitly.

• High · Outdated Android Support Library — library/libs/android-support-v4.jar, sample/libs/android-support-v4.jar, pom.xml (support-v4 dependency). The project uses android-support-v4.jar which is an old version of the Android Support Library. The support-v4 library has been deprecated and replaced with AndroidX. Multiple security patches and bug fixes have been released since this library was current, and vulnerabilities may exist in the older version. Fix: Migrate to AndroidX libraries. Replace com.google.android:support-v4 with androidx.viewpager:viewpager and androidx.appcompat:appcompat. Update all related imports in source files.
• High · Missing Dependency Version Specification — library/pom.xml (parent dependency reference, actual parent: pom.xml). The parent pom.xml file is not provided, but the library/pom.xml references a parent version without specifying exact versions for dependencies. This can lead to unpredictable builds and potential use of vulnerable dependency versions if the parent POM uses version ranges or defaults. Fix: Explicitly specify all dependency versions in the pom.xml. Avoid using version ranges and always pin to specific, vetted versions. Review the parent pom.xml to ensure all transitive dependencies are properly versioned.
• Medium · Obsolete Build Tools and Android API Levels — library/pom.xml (apklib packaging), library/project.properties, sample/project.properties. The project structure suggests use of very old Android development tooling (apklib packaging, old maven-android-plugin). This indicates the project targets outdated Android API levels and uses deprecated build methods. Modern security practices and patches are not applied. Fix: Update to modern Android build system (Gradle with Android Gradle Plugin). Update target API level to current standards (API 34+). Migrate from apklib to aar packaging format.
• Medium · Missing Security Dependencies Analysis — library/pom.xml (plugin definitions). The pom.xml does not explicitly declare versions for the android-maven-plugin and maven-checkstyle-plugin. These are critical build-time security tools that should be explicitly versioned and regularly updated to catch security issues. Fix: Add explicit version tags to all Maven plugins. Use recent stable versions of android-maven-plugin (or migrate to Gradle) and maven-checkstyle-plugin (3.x+). Pin plugin versions for reproducible builds.
• Low · No HTTPS Repository Configuration — pom.xml, library/pom.xml. The pom.xml references external dependencies but does not explicitly configure repository URLs with HTTPS. Older Maven configurations may default to HTTP repositories, which could be vulnerable to man-in-the-middle attacks during dependency downloads. Fix: Explicitly configure all repository URLs in pom.xml to use HTTPS. Include repository mirror configuration in settings.xml to enforce secure connections. Consider using a private artifact repository with checksum verification.

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.