Apache Cordova
Apache Cordova is an open-source mobile development framework governed by the Apache Software Foundation that enables developers to build mobile applications using standard web technologies — HTML, CSS, and JavaScript. It bridges web code to native device capabilities through a plugin architecture, targeting iOS, Android, Electron, and Browser platforms from a single codebase.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Apache Cordova the way a machine reads it — 36 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Apache Cordova scores 51.3/100 (developing), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Apache Cordova
Each block below is one kind of artifact we hold for Apache Cordova. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Apache Cordova
Apache Cordova provides a JavaScript plugin API for accessing native device capabilities (camera, GPS, file system, contacts, etc.), a CLI for project management and multi-platf...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Apache Cordova Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Apache Cordova Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Plugin Architecture
Extensible plugin system that bridges JavaScript to native device APIs for camera, GPS, file system, contacts, battery, and more.
Cross-Platform CLI
Command-line interface for creating, building, testing, and deploying applications to multiple platforms from a single codebase.
Native Device Access
Access to native hardware capabilities including camera, geolocation, network information, vibration, media capture, and device info.
WebView-Based Runtime
Renders applications in a native WebView, enabling web technologies to run as native mobile apps on iOS, Android, and Electron.
Plugin Development API
Full API for creating custom native plugins in Swift/Objective-C (iOS) and Java/Kotlin (Android) that expose device APIs to JavaScript.
Allowlist Security
Built-in allowlist mechanism for controlling which URLs and resources the application is permitted to access.
Semantic Vocabularies 3
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Apache Cordova API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Apache Cordova Camera Options Structure
JSON STRUCTUREApache Cordova Config Widget Structure
JSON STRUCTUREApache Cordova Geolocation Position Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Cross-Platform Mobile Apps
Build iOS and Android apps from a single HTML/CSS/JavaScript codebase, reducing development time and cost.
Hybrid App Development
Combine web application UIs with native device capabilities for apps that need both web flexibility and native hardware access.
Enterprise Mobile Solutions
Rapidly prototype and deploy enterprise mobile applications leveraging existing web development skills.
Desktop Apps via Electron
Package web apps as Electron desktop applications using the same Cordova plugin model.
IoT and Device Interfaces
Interface with Bluetooth, sensors, and other hardware through community and custom Cordova plugins.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Ionic Framework
Ionic uses Cordova (and Capacitor) as its native runtime, providing UI components on top of the Cordova platform.
Adobe PhoneGap
PhoneGap was a commercial distribution of Apache Cordova, now retired, but helped establish the Cordova ecosystem.
npm Package Registry
Cordova plugins and the CLI are published and distributed via npm, the Node.js package registry.
Gradle (Android)
Android platform builds use Gradle for dependency management and compilation.
Xcode (iOS)
iOS platform builds require Xcode for compilation, signing, and deployment.
Electron
Cordova-Electron platform target allows packaging Cordova apps as desktop Electron applications.
Resources
Every other property we hold for Apache Cordova — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/apache-cordova · machine-readable index on apis.io