RepoPilot

Tencent/Hippy

Hippy is designed to easily build cross-platform dynamic apps. 👏

Mixed

Evidence incomplete — review before adopting

MixedDependency

test evidence incomplete; dependency CVE scan unavailable

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

dependency CVE scan unavailable

  • Concentrated ownership — top contributor handles 65% of recent commits
  • Could not verify tests from the available repository evidence
  • Last commit 2w ago
  • 7 active contributors
  • Apache-2.0 licensed
  • CI configured

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Informational only. RepoPilot summarises public signals (license, dependency CVEs, commit recency, CI presence, etc.) at the time of analysis. Signals can be incomplete or stale. Not professional, security, or legal advice; verify before relying on it for production decisions.

Repository brief

Repo brief: Tencent/Hippy

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T01:48:03.337Z · commit ff17a50c6c18

Verdict

Mixed — Evidence incomplete — review before adopting

  • Last commit 2w ago
  • 7 active contributors
  • Apache-2.0 licensed
  • CI configured

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Hippy is a cross-platform development framework that lets developers write JavaScript/TypeScript once (using React or Vue) and deploy to iOS, Android, Web, and other platforms. It compiles to native code with a JS engine binding layer, enabling apps like Mobile QQ, Tencent Video, and QQ Music to reach hundreds of millions of users while maintaining write-once performance. Monorepo architecture: core/ contains the C++/Java VM binding layer and layout engine (using Tencent's taitank flex layout); driver/ has platform implementations (iOS, Android, Web); modules/ provides recyclable UI components; examples/ contains React/Vue demo apps; separate devtools/, docs/, and build/

Start here

Open these first:

  • README.md — Framework overview and getting started guide—defines Hippy's cross-platform value proposition and architectural intent
  • build.gradle — Root Gradle configuration managing Android build and dependency resolution across the entire project
  • .github/workflows/android_build_tests.yml — CI/CD pipeline for Android builds—enforces quality gates and integration test coverage
  • .github/workflows/frontend_build_tests.yml — CI/CD pipeline for frontend/JS builds—validates cross-platform JavaScript transpilation and bundling
  • buildconfig/cmake/GlobalPackagesModule.cmake — CMake configuration for native module management—coordinates C++ compilation across iOS, Android, and Linux targets

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/Tencent/Hippy.git
cd Hippy
git lfs install && git lfs pull  # Required for .so, .gz, .otf files
npm install
# For iOS: cd examples/hippy-react-demo && npm run build:ios
# For Android: cd examples/hippy-react-demo && npm run build:android

Daily commands:

After npm install: npm run build (compiles TypeScript), then platform-specific: iOS simulator: cd examples/hippy-react-demo && npm run build:ios && open build/HippyDemo.xcodeproj; Android: npm run build:android

…shortened for this brief.

Key cautions & unknowns

  • Concentrated ownership — top contributor handles 65% of recent commits
  • Could not verify tests from the available repository evidence
  • git-lfs required: .so, .gz, .otf files are LFS-tracked; skipping git lfs install causes silent build failures. NDK + Xcode mandatory: local Android/iOS builds require specific NDK version (check…
  • Published-advisory coverage was unavailable for the captured dependencies.
  • Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.


For the complete agent context, use the CLAUDE.md or Cursor rules export.

Save as

Full context for agent files, or a concise PDF for human review.

View complete agent reference

Open to load every section of the agent reference.

Want this for your own repo?

Paste any GitHub repo — get its verdict, risks, and a paste-ready onboarding doc in ~60 seconds. Free, no sign-up.

Embed the "Forkable" badge

Paste into your README — live-updates from the latest cached analysis.

Variant:
RepoPilot: Forkable
[![RepoPilot: Forkable](https://repopilot.app/api/badge/tencent/hippy?axis=fork)](https://repopilot.app/r/tencent/hippy)

Paste at the top of your README.md — renders inline like a shields.io badge.

Preview social card

This card auto-renders when someone shares https://repopilot.app/r/tencent/hippy on X, Slack, or LinkedIn.

Ask AI about tencent/hippy

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question
Embed this chat in your README

Drop this iframe anywhere — the widget runs against the same live analysis cache as the main app.

<iframe
  src="https://repopilot.app/embed/tencent/hippy"
  width="100%" height="500"
  style="border:1px solid #d0d7de; border-radius:8px;"
  allow="microphone"
  loading="lazy"
></iframe>