Skip to content

Build cross-platform Native Progressive Web Apps for iOS, Android, and the Web ⚡️

License

Notifications You must be signed in to change notification settings

Cap-go/capacitor-plus

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Capacitor+

An automated, always-synced fork of Capacitor


What is Capacitor+?

Capacitor+ is an automated fork of Capacitor maintained by Capgo. It stays in sync with the official Capacitor repository through a fully automated pipeline.

Philosophy

Capacitor+ exists to solve a fundamental problem: great PRs sitting unmerged in the official Capacitor repository.

The Ionic team maintains Capacitor with their own priorities and release schedule. This means community contributions - bug fixes, improvements, and features - can wait months or even years to be merged. Some never make it at all.

Capacitor+ takes a different approach:

  1. Merge PRs from Forks - We actively merge valuable PRs that are stuck in the upstream queue. If you have a fix that's been waiting, we can include it here.
  2. Continuous Sync - Every change from upstream Capacitor is automatically pulled, tested, and verified
  3. Rapid Releases - When changes pass CI, they're automatically published to npm under the @capacitor-plus scope
  4. Community-First - Your contributions matter. We prioritize merging community improvements.
  5. Transparency - All automation is open source and visible in this repository

Want Your PR Merged?

Have a PR stuck in the Capacitor repo? Here's how to get it into Capacitor+:

  1. Open an issue in this repo linking to your upstream PR
  2. Or submit the PR directly to the plus branch
  3. We'll review it, run CI, and merge it if it passes

This way, you and others can benefit from your work immediately, without waiting for the upstream release cycle.

How It Works

┌─────────────────────┐     ┌──────────────────┐     ┌──────────────────┐     ┌─────────────────┐
│  ionic-team/        │     │  CI/CD           │     │  Claude Code     │     │  npm publish    │
│  capacitor          │────▶│  Pipeline        │────▶│  Security Review │────▶│  @capacitor-plus│
│  (upstream)         │     │  (daily sync)    │     │  (AI analysis)   │     │  packages       │
└─────────────────────┘     └──────────────────┘     └──────────────────┘     └─────────────────┘
  1. Daily Sync: A GitHub Action fetches the latest changes from ionic-team/capacitor
  2. PR Creation: Changes are proposed as pull requests to the plus branch
  3. CI Validation: Full test suite runs (lint, unit tests, iOS build, Android build)
  4. Claude Code Review: AI-powered comprehensive security analysis checks for:
    • Security vulnerabilities (injection, XSS, etc.)
    • Breaking API changes
    • Crash risks and stability issues
    • Data integrity and privacy concerns
    • Malicious code patterns
  5. Auto-Merge: Only if CI passes AND Claude approves (no issues detected)
  6. Auto-Publish: A new version is published to npm under @capacitor-plus/*

Packages

Package npm
@capacitor-plus/core npm
@capacitor-plus/cli npm
@capacitor-plus/android npm
@capacitor-plus/ios npm

Installation

npm install @capacitor-plus/core @capacitor-plus/cli
npm install @capacitor-plus/android  # for Android
npm install @capacitor-plus/ios      # for iOS

Why Use Capacitor+?

  • Get Stuck PRs Now: Community fixes and features that are waiting in upstream? We merge them.
  • Stay Current: Get upstream fixes as soon as they pass CI
  • Security First: Every change is reviewed by Claude Code for vulnerabilities, breaking changes, and stability risks
  • Verified Releases: Only changes that pass both CI tests AND AI security review are published
  • Drop-in Replacement: Same API as Capacitor, just a different package scope
  • Your Voice Matters: Submit your own PRs or request specific upstream PRs to be merged

Security Review

Every upstream sync is analyzed by Claude Code for:

Check Description
Security Command injection, XSS, path traversal, hardcoded secrets, etc.
Breaking Changes Removed/renamed APIs, changed signatures, config format changes
Stability Null dereferences, unhandled exceptions, race conditions, memory leaks
Data Safety Data loss scenarios, privacy violations, insecure storage
Code Integrity Obfuscated code, suspicious network calls, backdoors

If any issues are detected, the PR is flagged for manual review and will NOT be auto-merged.


About Capacitor

Capacitor lets you run web apps natively on iOS, Android, Web, and more with a single codebase and cross-platform APIs.

Capacitor provides a cross-platform API and code execution layer that makes it easy to call Native SDKs from web code and to write custom native plugins that your app may need. Additionally, Capacitor provides first-class Progressive Web App support so you can write one app and deploy it to the app stores and the mobile web.

Capacitor comes with a Plugin API for building native plugins. Plugins can be written inside Capacitor apps or packaged into an npm dependency for community use. Plugin authors are encouraged to use Swift to develop plugins in iOS and Kotlin (or Java) in Android.

Getting Started

Capacitor was designed to drop-in to any existing modern web app. Run the following commands to initialize Capacitor in your app:

npm install @capacitor/core @capacitor/cli
npx cap init

Next, install any of the desired native platforms:

npm install @capacitor/android
npx cap add android
npm install @capacitor/ios
npx cap add ios

New App?

For new apps, we recommend trying the Ionic Framework with Capacitor.

To begin, install the Ionic CLI (npm install -g @ionic/cli) and start a new app:

ionic start --capacitor

FAQ

What are the differences between Capacitor and Cordova?

In spirit, Capacitor and Cordova are very similar. Capacitor offers backward compatibility with a vast majority of Cordova plugins.

Capacitor and Cordova differ in that Capacitor:

  • takes a more modern approach to tooling and plugin development
  • treats native projects as source artifacts as opposed to build artifacts
  • is maintained by the Ionic Team 💙😊

See the docs for more details.

Do I need to use Ionic Framework with Capacitor?

No, you do not need to use Ionic Framework with Capacitor. Without the Ionic Framework, you may need to implement Native UI yourself. Without the Ionic CLI, you may need to configure tooling yourself to enable features such as livereload. See the docs for more details.

Contributing

See CONTRIBUTING.md.

Contributors

Made possible by the Capacitor community. 💖

About

Build cross-platform Native Progressive Web Apps for iOS, Android, and the Web ⚡️

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Sponsor this project

  •  

Packages

No packages published

Languages

  • TypeScript 30.5%
  • Java 29.1%
  • Swift 23.3%
  • JavaScript 8.5%
  • Objective-C 7.8%
  • C 0.3%
  • Other 0.5%