PAM 1.0
PAM 1.0 turns the ecosystem into one contextual developer experience. Install one CLI, create a project, and use the same short commands for server, Laravel, native mobile, and desktop workflows.
Install
Section titled “Install”curl --proto '=https' --tlsv1.2 --fail --silent --show-error --location \ --output pam-install.sh \ https://github.com/push-in/pam/releases/download/v1.0.2/install.shsh pam-install.shrm pam-install.sh
pam --versionpam doctorThe installer verifies checksums and installs under ~/.local without root.
Official archives carry the exact private PHP Embed runtime and isolated INI
tree. Composer is signature-verified when first needed.
One CLI
Section titled “One CLI”The 1.0 command contract includes:
- interactive
pamlauncher andpam initpresets; - contextual
doctor,dev,run,logs,devices,test, andbuild; make:*generators for Native and Laravel;- package discovery and preflight through
packages,add,remove, andoutdated; - embedded
composerand Laravelartisanexecution; - formatting, linting, diagnostics, profiling, signing, packaging, and release gates;
- application and Composer-package command extension; and
.pamformatter/LSP setup for VS Code, Neovim, and Helix.
Native evidence
Section titled “Native evidence”Android is certified on APIs 26 and 36 with the real PHP Embed runtime, generated app, emulator execution, signed APK/AAB production artifacts, and checksums.
iOS is certified by generating a clean Xcode host, resolving official plugins after Composer dry-runs, building every target, installing and launching the application in a real simulator, and proving the embedded PHP process remains alive. The matrix covers PHP 8.4/iOS 15 and PHP 8.5/iOS 18 with Share Extension, Health, Media, Widgets, App Intents, and Live Activities.
Application signing secrets are never committed. Android keystores and Apple certificates/provisioning remain in the application team’s environment.
Release artifacts
Section titled “Release artifacts”The GitHub release publishes checksum-paired archives for Linux x86_64,
Linux ARM64, macOS Apple Silicon, and macOS Intel, plus the verified installer.
The Apple Silicon archive includes both supported iOS PHP/XCFramework runtimes;
the Intel archive contains the verified PHP 8.4/8.5 macOS runtime. A separate,
attested Android bundle carries PHP 8.4/8.5 and prebuilt PAM Native engines for
ARM64 and x86_64; pam doctor --fix installs it on demand.
The six server Composer packages are split into immutable public repositories
and published on Packagist under the organization-owned pushinbr/pam-*
namespace. v1.0.2 is the recommended 1.0 patch: besides completing this
public package contract, new API applications now pass pam format --check,
pam lint, and pam test immediately after creation. PAM Native and its
plugins keep their own release cadence and declare explicit compatible version
ranges.
Verification
Section titled “Verification”- PAM 1.0.2 release
- PAM CI
- Android certification
- iOS certification
- Composer package publication
- PAM Native releases
The compatibility guide defines what these checks prove and what each application must still validate against its own packages, credentials, devices, data stores, and workloads.