pushinbr/pam-psr-bridge

PSR-7, PSR-15 and PSR-17 implementations for Pam.

Maintainers

Package info

github.com/push-in/pam-psr-bridge

Homepage

Issues

pkg:composer/pushinbr/pam-psr-bridge

Transparency log

Statistics

Installs: 58

Dependents: 1

Suggesters: 1

Stars: 0

Security

Advisories: 0

Aikido package health analysis

v1.0.2 2026-08-10 23:21 UTC

Requires

Apache-2.0 8a1ca2912bc24968582b081812b2f4caf2926efb

phppsr-7psr-17psr-15pam

Published on Packagist.org on 2026-08-11 00:51 UTC

This package is auto-updated.

Last update: 2026-08-11 14:15:25 UTC

README

PSR-7, PSR-15 and PSR-17 interoperability for Pam using the official PHP-FIG interfaces.

pam composer require pushinbr/pam-psr-bridge

Pass a PSR-15 handler and middleware to Pam\App::handler() and Pam\App::middleware(); Pam converts native requests and responses at the runtime boundary.

License

Free and open-source under the Apache License 2.0. You may use, modify, and distribute this package for any purpose, including commercially.

Recommended PAM workflow

Install inside an existing PAM project with pam composer require pushinbr/pam-psr-bridge. PAM performs the package operation through its private PHP runtime; a global PHP or Composer installation is not required.

Run pam doctor after dependency changes and before creating a release. The project remains a normal Composer project with a standard manifest, lockfile, PSR-4 autoloading, and vendor/autoload.php.

API guide

Surface Use it for
PSR-7 Convert PAM native requests and responses to the official HTTP message interfaces.
PSR-15 Run middleware and request handlers through App::middleware() and App::handler().
PSR-17 Use installed HTTP factories where a package requires standard message construction.
Runtime boundary Convert once at the edge while PAM retains native transport ownership.

Pass a PSR-15 handler to Pam\App::handler() and PSR-15 middleware to Pam\App::middleware(). Keep blocking-library behavior in mind: standards compatibility does not make synchronous package I/O asynchronous.

Production checklist

  • Keep request data and mutable state scoped to the current request.
  • Test success, validation failure, exception, cancellation, and timeout paths.
  • Configure explicit limits and avoid unbounded payloads, queues, or retained collections.
  • Run pam doctor, pam test, and the relevant integration suite before release.
  • Validate real dependencies and workload behavior; compatibility is not inferred from package installation alone.

Troubleshooting

  • Class not found: run pam composer install, verify PSR-4 configuration, and rerun pam doctor.
  • Behavior differs over the network: reproduce with PAM's transport integration tests; in-memory execution does not model the socket boundary.
  • A dependency blocks a worker: use PAM-native I/O, a compatible event loop, a process pool, or additional isolated workers.

Documentation and support

Report security vulnerabilities through GitHub private vulnerability reporting or the PAM security policy, not a public issue.