Skip to content
PAM

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.

Runtime, frameworks and applications

Section titled “Runtime, frameworks and applications”
Repository Role Canonical documentation
pam Persistent PHP runtime, CLI, packaging and release system Runtime and CLI
pam-api Optional HTTP application/router layer Package guide
pam-core-api 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-psr-bridge PSR-7/15/17 interoperability Package guide
pam-testing In-memory PAM API 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

Native platform and UI

Section titled “Native platform and UI”
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-mobile-ui Retained-native Material 3 component system Mobile UI and catalog
pam-mobile-ui-php Generated/distribution mirror of Mobile UI Distribution mirrors
pam-native-nitro Offline-first typed local data engine Nitro

Official Native integrations

Section titled “Official Native integrations”
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-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-laravel-sync 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-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-widgets Android/iOS home-screen widgets Widgets

Installation rule

Section titled “Installation rule”

Use PAM aliases for official application capabilities:

Terminal window
pam packages
pam add observability
pam add mobile-ui
pam doctor

pam composer require remains correct for normal server/framework packages such as pushinbr/pam-api and pushinbr/pam-laravel. Distribution mirrors are not separate installation choices.