Search by

pushinbr / pam-native-laravel-sync

This package is abandoned and no longer maintained. The author suggests using the pushinbr/pam-native-sync-laravel package instead.

Compatibility package for pushinbr/pam-native-sync-laravel.

Maintainers

Package info

github.com/push-in/pam-native-laravel-sync

Type:metapackage

pkg:composer/pushinbr/pam-native-laravel-sync

Transparency log

Statistics

Installs: 3

Dependents: 0

Suggesters: 0

Stars: 0

v0.2.1 2026-08-22 01:45 UTC

This package is auto-updated.

Last update: 2026-08-25 22:04:14 UTC


README

pushinbr/pam-native-laravel-sync

Compatibility package — do not use in new applications

This repository exists so older Composer projects keep installing safely. The maintained product is PAM Native Sync for Laravel.

Replacement Status

Use this instead

pam composer require pushinbr/pam-native-sync-laravel

PAM Native Sync for Laravel contains the active documentation, API examples, releases, issue tracker, and production guidance.

Why the name changed

The canonical name groups the server adapter under PAM Native Sync and matches the pam-native-<capability>-<adapter> package convention.

Migrate an existing project

Commit your current composer.json and composer.lock, then run:

pam composer remove pushinbr/pam-native-laravel-sync
pam composer require pushinbr/pam-native-sync-laravel
pam doctor

Run the application test suite before committing the new lockfile. Composer may continue to resolve this bridge transitively during a staged migration; application code should target the replacement package directly.

Support policy

  • No new features are added here.
  • Security or resolution fixes may be published only to preserve migration safety.
  • New documentation and issues belong to PAM Native Sync for Laravel.
  • The package is marked abandoned on Packagist in favor of pushinbr/pam-native-sync-laravel.

This explicit compatibility repository is intentional: old installs remain understandable without making the current PAM ecosystem ambiguous.