Download the PHP package maatify/event-logging without Composer
On this page you can find all versions of the php package maatify/event-logging. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Table of contents
Download maatify/event-logging
More information about maatify/event-logging
Files in maatify/event-logging
Download maatify/event-logging
More information about maatify/event-logging
Files in maatify/event-logging
Vendor maatify
Package event-logging
Short Description Framework-agnostic standalone event logging library containing isolated Maatify logging domains. Depends only on explicit Composer/runtime dependencies.
License MIT
Homepage https://github.com/Maatify/event-logging
Package event-logging
Short Description Framework-agnostic standalone event logging library containing isolated Maatify logging domains. Depends only on explicit Composer/runtime dependencies.
License MIT
Homepage https://github.com/Maatify/event-logging
FAQ
After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
Example:
Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
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.
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 PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
- 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.
Please rate this library. Is it a good library?
Informations about the package event-logging
# Maatify Event Logging
[](https://packagist.org/packages/maatify/event-logging)
[](https://packagist.org/packages/maatify/event-logging)
[](LICENSE)
[](https://github.com/Maatify/event-logging)
[](https://packagist.org/packages/maatify/event-logging)
[](https://packagist.org/packages/maatify/event-logging)
[](https://github.com/Maatify)
[](https://packagist.org/packages/maatify/event-logging)
[](CHANGELOG.md)
[](EVENT_LOGGING_PACKAGE_REFERENCE.md)
[](SECURITY.md)
[](CONTRIBUTING.md)
`maatify/event-logging` is a framework-agnostic standalone Composer package for registering event logging domains within the Maatify ecosystem.
This package provides strict domain isolation, MySQL persistence, and fail-open/fail-closed semantics without mandatory framework bindings. It intentionally relies on explicit Composer and runtime dependencies to operate autonomously from host applications and frameworks.
🚀 Key Features
- Six Isolated Logging Domains: Explicit boundaries for audit, tracing, signals, and operations.
- Domain-Specific Recorders: Tailored commands, DTOs, and repositories per domain.
- MySQL-Only Persistence: Direct database persistence through domain-owned repositories.
- AuthoritativeAudit Semantics: Fail-closed governance logging.
- Fail-Open Boundaries: Non-authoritative domains can accept a PSR-3 fallback logger.
- Optional Framework-Agnostic Provider and Bindings: Built-in optional factories and pure-PHP DI binding helpers for wiring dependencies.
- Primitive Cursor-Based Read APIs: Dedicated, stable read/query capabilities.
- No Mandatory Framework Bindings: Optional bindings are pure PHP convenience helpers and do not add framework runtime dependencies.
- No Generic Logging API: Excludes shared generic loggers, generic log tables, or unified repositories.
📋 Requirements
- PHP
^8.2 ext-jsonext-pdo
Composer/Runtime Dependencies:
psr/logramsey/uuidmaatify/exceptionsmaatify/shared-common
📦 Installation
📖 Usage
Factory / Provider Wiring
Host applications provide their own dependencies (PDO, Clock, PSR-3 Logger) to instantiate the domain provider:
(See 01-factory-provider.php for manual factory/provider wiring. Hosts that prefer DI can also import the optional pure-PHP Maatify\EventLogging\Bootstrap\EventLoggingBindings::definitions() helper; this helper is not required and does not introduce framework-specific behavior.)
Domain Recorder Usage
Recording an authoritative audit (fail-closed, requires robust persistence):
(See 04-audit-trail-record.php for broader examples.)
🏗️ Logging Domains
The package maintains six separated event domains:
- AuthoritativeAudit — Governance/security posture logging with fail-closed semantics.
- AuditTrail — Reads, views, exports, and navigation visibility events.
- SecuritySignals — Authentication and security anomaly signals.
- BehaviorTrace — Operational activity and mutation-only behavior events.
- DiagnosticsTelemetry — Technical observability and diagnostic events.
- DeliveryOperations — Async jobs, notifications, webhooks, and delivery lifecycle events.
🛡️ Architecture Guarantees
- Framework-Agnostic: Operates without any dependency on external framework containers or routes.
- Standalone Execution: Complete isolation from host application codebases.
- Domain Isolation: Every logging domain has exclusive ownership over its DTOs, tables, and policies.
- Host-Provided PDO: Database connections must be injected; the package does not manage connection lifecycles.
- MySQL-Only: Relies purely on MySQL schema without SQLite fallback support.
- Explicit Dependencies Only: Avoids zero-dependency assumptions; explicit runtime requirements ensure robustness.
- No Generic Paradigms: The package does not expose a catch-all logger, generic recorder, generic repository, or shared generic log table. PSR-3 is used only as an optional fallback logger for fail-open domains.
🧪 Examples
The examples/ directory contains plain PHP illustrative skeletons covering integration scenarios. See the Examples Coverage Plan for full context.
01-factory-provider.php02-manual-wiring.php03-authoritative-audit-record.php09-admin-read-audit-trail.php11-cursor-pagination.php13-psr-fallback-logger.php
📚 Documentation
- Event Logging Package Reference
- Schema Layout
- Testing Strategy
Architecture
- Unified Logging Architecture
- Logging Domain Rules
- CI Workflow Standard
- Storage & Schema Guarantees
- Deferred Scope & Future Considerations
- Authoritative Audit Pipeline
- Admin Query API Roadmap
Integration Guides
- Installation Guide
- Factory Usage
- Manual Wiring
- DI Bindings
- Admin Read Usage
✅ Quality Status
- PHP 8.2+
- PHPStan Level Max
- PHPUnit testing available
- GitHub Actions CI validated
🪪 License
This package is licensed under the MIT License. See the LICENSE file for details.
👤 Author
Engineered by Mohamed Abdulalim (@megyptm)
Backend Lead & Technical Architect
https://www.maatify.dev
[Built with ❤️ by Maatify.dev — Unified Ecosystem for Modern PHP Libraries](https://www.maatify.dev)
All versions of event-logging with dependencies
PHP Build Version
Package Version
Requires
php Version
^8.2
ext-json Version *
ext-pdo Version *
psr/log Version ^3.0
ramsey/uuid Version ^4.9
maatify/exceptions Version ^1.1
maatify/shared-common Version ^1.0
ext-json Version *
ext-pdo Version *
psr/log Version ^3.0
ramsey/uuid Version ^4.9
maatify/exceptions Version ^1.1
maatify/shared-common Version ^1.0
The package maatify/event-logging contains the following files
Loading the files please wait ...