Skip to content

PAM public repository map

This map prevents public code from becoming undiscoverable. Every public push-in/pam* repository has a product role and a canonical documentation destination.

Repository Role Canonical documentation
pam Persistent PHP runtime, CLI, packaging and release system Runtime and CLI
pam-http Optional HTTP application/router layer Package guide
pam-contracts Minimal extension contracts Package guide
pam-laravel Laravel lifecycle, operations and production tooling Laravel platform and API reference
pam-socket Event API over native RFC 6455 WebSockets Package guide
pam-http-psr PSR-7/15/17 interoperability for PAM HTTP Package guide
pam-http-testing In-memory PAM HTTP test client Package guide
pam-skeleton Versioned API template used by pam init Skeleton guide
pam-desktop Native desktop shell, worker and PHP API Desktop and API contracts
pam-docs This documentation site and its validation gates Documentation contract
Repository Role Canonical documentation
pam-native Native runtime, Android/iOS renderers and PHP authoring API Native overview and PHP API index
pam-native-php Generated/distribution mirror of the Native PHP surface Distribution mirrors
pam-native-ui Retained-native Material 3 component system Native UI and catalog
pam-native-ui-php Generated/distribution mirror of Native UI Distribution mirrors
pam-native-nitro Offline-first typed local data engine Nitro
Repository Capability Guide
pam-native-auth Encrypted credential vault and PKCE Auth
pam-native-background-transfer Durable uploads and downloads Background Transfer
pam-native-bluetooth BLE scan, connection and GATT Bluetooth
pam-native-camera Professional native photo/video capture Camera
pam-native-canvas Retained native 2D graphics Canvas
pam-native-3d Filament and RealityKit scenes 3D
pam-native-devtools Development inspection integration DevTools package
pam-native-feature-flags Typed flags, snapshots and rollout evaluation Feature Flags
pam-native-firebase Firebase services and messaging bridge Firebase
pam-native-health Health data permissions and queries Health
pam-native-intents Android intents and iOS URL activities Intents
pam-native-sync-laravel Laravel-backed native synchronization Laravel Sync
pam-native-live-activities iOS Live Activities Live Activities
pam-native-maps Native maps, markers and camera control Maps
pam-native-media Camera, picker and media processing Media
pam-native-media-editor Native timeline composition and export Media Editor
pam-native-nfc NFC sessions and records NFC
pam-native-observability Vendor-neutral telemetry and crash context Observability
pam-native-payments Platform payment sheets Payments
pam-native-plugin-kit Authoring and validating Native plugins Plugin Kit
pam-native-realtime Realtime native client transport Realtime
pam-native-scanner Barcode and document scanning Scanner
pam-native-share-extension Platform share extensions Share Extension
pam-native-subscriptions Store subscriptions and entitlement state Subscriptions
pam-native-sync Offline mutation and synchronization primitives Sync
pam-native-testing Native integration testing utilities Native Testing
pam-native-video Native video playback Video
pam-native-gpu Programmable OpenGL ES and Metal rendering GPU
pam-native-widgets Android/iOS home-screen widgets Widgets

Use PAM Composer for every ecosystem package:

Terminal window
pam composer require pushinbr/pam-native-observability
pam composer require pushinbr/pam-native-ui
pam doctor

The same workflow applies to server, framework, native and desktop products. Distribution mirrors are not separate installation choices.

These repositories contain migration-only Composer metapackages. They remain public so existing lockfiles resolve safely, but every package is marked abandoned on Packagist with its canonical replacement:

Compatibility repository Canonical repository
pam-api pam-http
pam-core-api pam-contracts
pam-psr pam-http-psr
pam-psr-bridge pam-http-psr
pam-testing pam-http-testing
pam-mobile-ui pam-native-ui
pam-native-laravel-sync pam-native-sync-laravel