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/H07000223/FlycoTabLayout 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 — Looks unmaintained — solo project with stale commits

• MIT licensed
• ⚠ Stale — last commit 3y ago
• ⚠ Solo or near-solo (1 contributor active in 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 H07000223/FlycoTabLayout repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/H07000223/FlycoTabLayout.

What it runs against: a local clone of H07000223/FlycoTabLayout — 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 H07000223/FlycoTabLayout | 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 | 5 critical file paths still exist | Catches refactors that moved load-bearing code | | 5 | Last commit ≤ 1106 days ago | Catches sudden abandonment since generation |

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

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

# 4. Critical files exist
test -f "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/CommonTabLayout.java" \\
  && ok "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/CommonTabLayout.java" \\
  || miss "missing critical file: FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/CommonTabLayout.java"
test -f "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/SlidingTabLayout.java" \\
  && ok "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/SlidingTabLayout.java" \\
  || miss "missing critical file: FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/SlidingTabLayout.java"
test -f "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/SegmentTabLayout.java" \\
  && ok "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/SegmentTabLayout.java" \\
  || miss "missing critical file: FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/SegmentTabLayout.java"
test -f "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/listener/CustomTabEntity.java" \\
  && ok "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/listener/CustomTabEntity.java" \\
  || miss "missing critical file: FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/listener/CustomTabEntity.java"
test -f "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/listener/OnTabSelectListener.java" \\
  && ok "FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/listener/OnTabSelectListener.java" \\
  || miss "missing critical file: FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/listener/OnTabSelectListener.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 1106 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~1076d)"
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/H07000223/FlycoTabLayout"
  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).

FlycoTabLayout is an Android library providing three polished TabLayout implementations: SlidingTabLayout (ViewPager-dependent with animated indicators), CommonTabLayout (ViewPager-independent with flexible fragment management), and SegmentTabLayout. It extends basic tab functionality with customizable indicators, unread message badges, icon support, and pre-built gesture handling. Monolithic Android library: FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/ contains three core TabLayout classes (SlidingTabLayout.java, CommonTabLayout.java, SegmentTabLayout.java), with supporting listener interfaces (OnTabSelectListener, CustomTabEntity), utility helpers (FragmentChangeManager, UnreadMsgUtils), and layout XMLs for different orientations (layout_tab_top.xml, layout_tab_bottom.xml, etc). Sample app under app/ demonstrates each implementation.

Android developers building tabbed navigation UIs who need production-ready, feature-rich tab implementations without building custom views. Particularly useful for apps requiring non-standard indicator styles, icon+text tabs, or badge notifications without coupling to ViewPager.

Moderately mature with 3.0.0 released Sept 2021 (AndroidX migration). The library is 128KB of production Java with clear API design and sample app demonstrating all three implementations. However, the last visible activity is ~2+ years ago, and there's no evidence of continuous CI/CD or test automation in the provided config.

Low immediate risk but aging codebase: no visible test suite in file structure, no CI configuration shown, and last update was 2021 (AndroidX baseline). Single maintainer (H07000223) with no obvious succession plan. Dependency surface is minimal (AppCompat, Support v4, Design library), but AndroidX-only support means pre-AndroidX projects cannot use v3.0.0.

No active development visible in provided data. Last changelog entry is 3.0.0 (Sept 2021). The library appears stable but not actively maintained—no PRs, issues, or recent commits are indicated.

git clone https://github.com/H07000223/FlycoTabLayout.git && cd FlycoTabLayout && ./gradlew build. No npm or custom scripts needed; standard Android Gradle build. Then ./gradlew installDebug to deploy sample app to emulator/device.

Daily commands: ./gradlew assembleDebug to build the library AAR. ./gradlew :app:installDebug to run the sample app on a connected device or emulator. No dev server; this is a compiled Android library.

• FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/CommonTabLayout.java — Core ViewGroup implementation for independent tab layout; foundational class that does not depend on ViewPager and supports icons, indicators, and unread message badges.
• FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/SlidingTabLayout.java — Primary TabLayout for ViewPager integration with custom indicator animations and unread message support; heavily customized from PagerSlidingTabStrip.
• FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/SegmentTabLayout.java — Specialized segment-style tab layout variant; third major TabLayout type in the library's public API.
• FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/listener/CustomTabEntity.java — Data model interface for tab metadata (title, icon, unread count); required by all three TabLayout implementations.
• FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/listener/OnTabSelectListener.java — Callback interface for tab selection events; primary integration point for activity/fragment logic.
• FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/utils/FragmentChangeManager.java — Helper utility for managing Fragment transactions with ViewPager; used by SlidingTabLayout convenience methods.
• FlycoTabLayout_Lib/src/main/res/values/attrs.xml — XML attribute definitions for all three TabLayout variants; essential for understanding customization options in layout files.

Add a new TabLayout variant

1. Create new class extending the appropriate base class (e.g., ViewGroup if ViewPager-independent, or reference SlidingTabLayout if ViewPager-dependent) (FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/YourNewTabLayout.java)
2. Define custom XML attributes for the new variant (FlycoTabLayout_Lib/src/main/res/values/attrs.xml)
3. Create corresponding tab item layout file following the naming convention (FlycoTabLayout_Lib/src/main/res/layout/layout_tab_variant.xml)
4. Implement OnTabSelectListener callback support in the variant class (FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/YourNewTabLayout.java)
5. Add demo Activity to sample app showing usage with CustomTabEntity data model (app/src/main/java/com/flyco/tablayoutsamples/ui/YourNewTabActivity.java)

Integrate SlidingTabLayout with ViewPager and Fragments

1. In your Activity, obtain references to SlidingTabLayout and ViewPager (app/src/main/java/com/flyco/tablayoutsamples/ui/SlidingTabActivity.java)
2. Create ArrayList of Fragment instances and array of tab titles (app/src/main/java/com/flyco/tablayoutsamples/ui/SlidingTabActivity.java)
3. Call convenience method: tabLayout.setViewPager(viewPager, titles, activity, fragments) (FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/SlidingTabLayout.java)
4. Implement OnTabSelectListener to handle tab selection callbacks (FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/listener/OnTabSelectListener.java)

Add unread message badges to tabs

1. Implement CustomTabEntity with unread count value in tabEntity.getUnreadNum() (app/src/main/java/com/flyco/tablayoutsamples/entity/TabEntity.java)
2. Use UnreadMsgUtils methods to display/update badge: setMsgCount(), setHasMsg(), etc. (FlycoTabLayout_Lib/src/main/java/com/flyco/tablayout/utils/UnreadMsgUtils.java)
3. MsgView will automatically render badges; configure attrs in layout file (msgTextColor, msgSize, etc.) (FlycoTabLayout_Lib/src/main/res/values/attrs.xml)

Customize indicator animation and appearance

1. In your Activity/Fragment XML layout, set attributes on CommonTabLayout or SlidingTabLayout (FlycoTabLayout_Lib/src/main/res/values/attrs.xml)
2. Common customization attrs: tl_indicator_style, tl_indicator_height, tl_indicator_width, tl_indicator_color, tl_indicator_margin_left, tl_indicator_margin_right (FlycoTabLayout_Lib/src/main/res/values/attrs.xml)
3. For icon-based tabs, use tl_icon_gravity (left, top, right, bottom) and tl_icon_width/height (FlycoTabLayout_Lib/src/main/res/values/attrs.xml)
4. Apply colors via tl_textSelectColor, tl_textUnSelectColor, and indicator animation will trigger on tab selection automatically (app/src/main/java/com/flyco/tablayoutsamples/ui/CommonTabActivity.java)

• Android ViewPager (optional) — SlidingTabLayout optionally integrates with ViewPager for synchronized page/tab navigation; CommonTabLayout deliberately avoids this dependency for flexibility
• Custom View & ViewGroup — TabLayout implementations extend ViewGroup to provide direct control over tab item layout, indicator rendering, and gesture handling without relying on native Android TabLayout
• Fragment transactions — FragmentChangeManager automates Fragment switching for apps using ViewPager + Fragments, reducing boilerplate in consumer code
• Custom XML attributes — attrs.xml enables declarative configuration of colors, dimensions, animations, and indicator styles in layout files rather than programmatic setup

• Separate CommonTabLayout from SlidingTabLayout rather than unifying under one abstraction

  • Why: ViewPager-dependent and independent use cases have different layout, measurement, and event propagation requirements
  • Consequence: Code duplication in core logic but clearer API contracts; developer must choose appropriate variant upfront

• No native Android support library dependency (e.g., com.android.support:design:*)

  • Why:
  • Consequence: undefined

No Proguard rules enforced in library build (minifyEnabled false), so obfuscation behavior is untested. CustomTabEntity requires both selected and unselected drawable icons (two-state model); passing null/single drawable may cause NPEs. Fragment transaction timing: FragmentChangeManager commits synchronously, which can cause ANRs if tabs are switched rapidly. Indicator animations assume View measure/layout has completed; calling setTabData() before parent ViewGroup is laid out produces unpredictable positioning. No dependency on AndroidX Design library SegmentedButtonGroup (newer Android), so this library's SegmentTabLayout is custom and unsupported post-API 29.

• ViewPager Scroll Listener Pattern — SlidingTabLayout synchronizes indicator position with ViewPager scroll via OnPageChangeListener callbacks; understanding this pattern is essential to modifying indicator animation behavior
• Fragment State Management & Transaction Commits — CommonTabLayout manages Fragment lifecycles via FragmentChangeManager; misunderstanding commit() vs commitNow() and fragment state can cause memory leaks or UI glitches when tabs are switched
• Android Custom Attributes (attrs.xml) & TypedArray — All three TabLayout variants are customized via attrs.xml attributes parsed at inflation time; modifying styling requires understanding how TypedArray extracts and applies custom properties
• Drawable State Lists & Multi-State Icons — CustomTabEntity assumes selected/unselected drawable pairs; understanding Android StateListDrawable is required to properly theme tabs with state-aware icons
• Canvas-based Custom Drawing & Path Animation — Indicator rendering (NORMAL, TRIANGLE, BLOCK styles) uses Canvas drawing with Path objects; extending indicator styles requires custom onDraw() implementation
• ViewGroup Layout Measurement & Positioning — Tab width calculation and indicator positioning depend on correct onMeasure() and onLayout() sequences; bugs in indicator placement often stem from incorrect measure specs or layout timing
• Badge/Notification Pattern (MsgView) — UnreadMsgUtils and MsgView implement a small-footprint badge system for unread counts; useful for understanding non-Material approaches to notification indicators on tab items

• jpardogo/PagerSlidingTabStrip — Direct predecessor and inspiration for SlidingTabLayout; original library that FlycoTabLayout forked and heavily extended with indicators and badges
• astuetz/PagerSlidingTabStrip — Alternative fork of PagerSlidingTabStrip with different feature priorities; useful for comparing design decisions in ViewPager tab libraries
• google/material-components-android — Official Google Material Design TabLayout component; modern replacement for many use cases, though less customizable than FlycoTabLayout
• angcyo/DslViewPager — Contemporary Chinese Android library for ViewPager + tab binding; similar target audience, alternative implementation patterns

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 AndroidX migration support and deprecation warnings

The library currently depends on legacy Android Support Library (support.appcompat, support.v4, support.design) which is deprecated. AndroidX is the modern replacement and many apps have already migrated. Adding AndroidX support with backward compatibility would make this library usable in modern Android projects. This involves updating build.gradle dependencies, testing against AndroidX, and potentially providing migration documentation.

• [ ] Update FlycoTabLayout_Lib/build.gradle to add AndroidX dependencies alongside legacy support libraries using compatibility flags
• [ ] Update FlycoTabLayout_Lib/src/main/AndroidManifest.xml to declare android.useAndroidX=true support
• [ ] Test all three TabLayout implementations (SlidingTabLayout, CommonTabLayout, SegmentTabLayout) with sample app against AndroidX dependencies
• [ ] Add migration guide to README.md documenting the transition path for users

Add unit tests for TabLayout selection and state management

The library has no visible test files despite having complex state management (tab selection, unread message indicators, fragment switching via FragmentChangeManager). Testing the core functionality of OnTabSelectListener callbacks, UnreadMsgUtils badge logic, and tab selection state would catch regressions and improve maintainability.

• [ ] Create app/src/test/java/com/flyco/tablayoutsamples/ directory structure for unit tests
• [ ] Add unit tests for CustomTabEntity and OnTabSelectListener interface implementations
• [ ] Add unit tests for UnreadMsgUtils.java to verify badge/unread message display logic
• [ ] Add unit tests for FragmentChangeManager.java to verify fragment switching and lifecycle management
• [ ] Update app/build.gradle to include testing dependencies (JUnit, Mockito, AndroidX Test)

Add GitHub Actions CI workflow for automated builds and testing

The repository lacks automated testing infrastructure. A CI pipeline would validate pull requests against multiple Android SDK versions, catch build failures early, and ensure the library compiles correctly. This is especially important given the library's support library dependencies and the need to verify AndroidX compatibility.

• [ ] Create .github/workflows/android-build.yml with gradle build steps for both FlycoTabLayout_Lib and app modules
• [ ] Configure the workflow to test against multiple Android API levels (minSdkVersion through latest stable)
• [ ] Add lint checks to detect potential issues (run ./gradlew lint)
• [ ] Configure the workflow to run on pull requests and pushes to main branches
• [ ] Add build status badge to README.md linking to the Actions workflow

• Add JUnit4 test coverage for FragmentChangeManager and UnreadMsgUtils (currently 0% coverage visible); start with unit tests for fragment replace/add transaction edge cases
• Extend attrs.xml documentation with examples showing how each attribute (e.g., tl_indicator_style TRIANGLE) renders visually; add inline code snippet in README showing custom Drawable setup
• Refactor SlidingTabLayout's onPageScrolled() method to expose a callback hook for custom scroll-linked animations; currently hardcoded animation behavior makes subclassing difficult

The FlycoTabLayout library has a relatively clean security posture as a UI component library. No critical injection vulnerabilities, hardcoded secrets, or infrastructure misconfigurations were detected. However, there are moderate concerns regarding code obfuscation being disabled and the use of older/vague dependency versions. The main risks stem from build configuration practices rather than the library code itself. Recommendations focus on enabling ProGuard/R8 minification, updating dependencies to modern versions, and replacing deprecated support libraries with AndroidX equivalents.

• High · Outdated Gradle Maven Publish Plugin — FlycoTabLayout_Lib/build.gradle. The build.gradle file uses gradle-maven-publish-plugin version 0.18.0, which may contain known vulnerabilities. This plugin is used for publishing artifacts and should be kept up to date to avoid potential security issues in the build pipeline. Fix: Update to the latest version of com.vanniktech:gradle-maven-publish-plugin (check Maven Central for current version). Review the plugin's changelog for security fixes.
• Medium · Missing ProGuard Configuration in Debug Build — FlycoTabLayout_Lib/build.gradle. ProGuard minification is disabled in the release build (minifyEnabled false), which means code is not obfuscated. This makes reverse engineering easier and could expose sensitive business logic, algorithm implementations, or API patterns. Fix: Enable minification for release builds: change 'minifyEnabled false' to 'minifyEnabled true'. Ensure proguard-rules.pro is properly configured to keep necessary classes while obfuscating sensitive code.
• Medium · Vague Dependency Version Constraints — FlycoTabLayout_Lib/build.gradle, dependencies.gradle. The build.gradle uses variable references from rootProject.ext for SDK versions and dependencies (e.g., support.appcompat, support.v4, support.design). Without seeing the actual versions in dependencies.gradle, there's risk of using outdated support libraries with known vulnerabilities. Fix: Review dependencies.gradle and ensure all AndroidX/Support library versions are current. Replace deprecated Android Support Library with AndroidX equivalents. Pin versions explicitly or use version ranges cautiously.
• Low · File Tree Dependency Inclusion — FlycoTabLayout_Lib/build.gradle. The build.gradle includes all JAR files from the 'libs' directory without explicit version control: 'implementation fileTree(dir: 'libs', include: ['*.jar'])', which could potentially include unsigned or compromised JAR files. Fix: Replace fileTree dependencies with explicit, versioned dependencies from Maven Central or other trusted repositories. If local JARs are necessary, document their purpose and verify their integrity.
• Low · Missing Gradle Wrapper Validation — gradle/wrapper/gradle-wrapper.jar, gradle/wrapper/gradle-wrapper.properties. The gradle-wrapper.jar file is present in the repository. While this is common practice, ensure the Gradle wrapper is regularly updated and the wrapper's checksum is validated to prevent man-in-the-middle attacks during build time. Fix: Verify gradle-wrapper.properties contains a valid distributionSha256Sum. Regularly update the Gradle wrapper to the latest stable version using './gradlew wrapper --gradle-version=<VERSION>'.

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.