Download the PHP package kumwe/access-context without Composer
On this page you can find all versions of the php package kumwe/access-context. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download kumwe/access-context
More information about kumwe/access-context
Files in kumwe/access-context
Package access-context
Short Description Immutable Kumwe access-context values and actor contracts, supplied explicitly to every use case.
License Apache-2.0
Homepage https://github.com/kumwe/access-context
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package access-context
Kumwe Access Context
Immutable access-context values and actor contracts, supplied explicitly for each unit of work.
Requires PHP 8.5. The canonical namespace is Kumwe\Context; there are no runtime package dependencies.
The package carries established actor, site, organization, workspace, membership, authentication and trace facts. The host authenticates, resolves membership, validates provenance and makes every authorization decision. It does not provide grants, capability policies, credentials, sessions, persistence or ambient context lookup.
Installation and standalone use
After the first verified release is available on Packagist:
For the source checkout, run composer install, then this complete example:
Run composer examples for human, background and step-up examples. Their host identities are illustrative;
production authentication and the set of permitted system actors belong to the consuming application.
Construction and lifetime
There is no ConfigProvider, factory registration, service alias or configuration key. These are values, enums,
contracts and one exception; register host adapters in the composition root and pass contexts as operation
arguments.
Never register a shared current actor, membership, request or tenant service. Implement Contract\Principal and
Contract\SystemActor over the host's established identity model. Principal implementations must remain immutable
for the unit of work and compare provenance by object identity.
Public surface
ExecutionContext: explicit human/system issuance, scope facts, child contexts, fingerprints and redacted exports.SiteContext,OrganizationContext,WorkspaceContext,MembershipContext: distinct bounded scope facts.AuthenticationStrength,AuthenticatedSurface,StepUpProof: authentication facts and freshness bindings.Principal,SystemActor: host implementation ports.InvalidContext: consistent argument refusal; messages identify the rule without echoing submitted input.
architecture,
migration handoff.
The three manifests under resources/ record every exported symbol, semantic capability and provider decision.
Guarantees and limits
Scopes normalize by trimming/lowercasing before their 191-character grammar check; site and organization remain different types. Contexts hold exactly one human or explicit system actor. Background contexts cannot impersonate human strength or another surface. A workspace proof requires an organization. Multi-factor contexts require a proof bound to actor, session, site, organization, workspace and security epoch.
StepUpProof::isValidFor() checks its supplied actor/session/site/organization and trusted time interval only.
The host must additionally enforce workspace, purpose, epoch, method, nonce consumption and policy at action time.
Expiry is exclusive; verification is inclusive; intervals cannot exceed fifteen minutes. No method reads a clock.
Fingerprints are deterministic and credential-sensitive or approval-stable as documented; they are not credentials.
toArray() omits provenance, session identifiers, proof nonces and fingerprints. PHP object serialization is not a
trusted transport or storage format; only explicit redacted exports are supported for logging.
The package performs no I/O, transaction, authorization, retries or membership refresh. App must refresh security and membership state inside the actual mutation transaction and preserve the three-database/integration test lane.
Development and release
The full gate includes PHPStan max/strict rules, coding/member documentation checks, behavior/API/architecture
tests,
security audit, release-record parser and an exact archive installed as a dependency in an isolated no-dev
consumer.
The tooling additionally needs mbstring, tokenizer, XMLWriter and ZIP; these are development requirements, not
runtime dependencies of the value package. composer clean-consumer runs the artifact check separately.
The portable extraction is implemented and 0.1.1 is published. This successor hardens serializable identities; its human review, publication and independent release verification remain required before App adoption. Releasing and compatibility describes immutable release-on-record and exact pre-1.0 pins. LICENSE.
Raw control bytes in site, organization and workspace inputs are rejected before whitespace normalization. This includes leading/trailing NUL, tabs, newlines, carriage returns and DEL; valid space-padded values still normalize.
