Download the PHP package kumwe/access-control without Composer
On this page you can find all versions of the php package kumwe/access-control. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download kumwe/access-control
More information about kumwe/access-control
Files in kumwe/access-control
Package access-control
Short Description Portable authorization decisions, owner-bound policy registries, scopes and explicit authority ports.
License Apache-2.0
Homepage https://github.com/kumwe/access-control
Informations about the package access-control
Kumwe Access Control
Portable authorization decisions, owner-bound capability/resource-policy registries, scope models and explicit host
authority ports. Canonical PHP namespace: Kumwe\Access\. Requires PHP 8.5, exact Access Context 0.1.2 and
PSR Container 2. No native extension is required.
Installation and use
Install the published package with an exact pre-1.0 pin:
Deny overrides step-up, step-up overrides allow, and abstention grants nothing. Equal-state decisions select policy then reason in byte order. Empty input explicitly abstains. The host evaluates rules and enforces the resulting authority; this package has no authentication or audit implementation.
Registries require explicit MembershipRequirement and ownership rules require an explicit reserved host table.
Unknown ownership categories default to site-only. Extension capabilities obey their owner namespace, cannot bind
another owner's capability or declare system identities, and collide regardless of lifecycle. Removing capability
ownership makes orphan policy lookups inert.
Core integration
Register ConfigProvider in Core's composition root with explicit membership targets, reserved ownership rules and reference inspectors. Core supplies authority, membership resolution, persistence, transactions and audit adapters. See the integration guide for service lifetimes, configuration and retained integration tests.
charter, security policy describe supported boundaries. Published versions and CI status are linked above; Core integration is validated in the consuming repository.
Development and releases
CI installs the built ZIP as a no-development, authoritative-classmap dependency and exercises every export, example and configured service. Testing explains package and Core ownership. dependency verification distinguish publication identity checks from independent consumer evidence. Licensed under Apache-2.0.