PHPackages                             stegeman/symfony-messenger-cloud-events - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [API Development](/categories/api)
4. /
5. stegeman/symfony-messenger-cloud-events

ActiveBundle[API Development](/categories/api)

stegeman/symfony-messenger-cloud-events
=======================================

Symfony Messenger Cloud Events

1.1.7(6d ago)01.1kMITPHPPHP ^8.2|^8.3|^8.4

Since Jul 14Pushed 6d ago1 watchersCompare

[ Source](https://github.com/stegeman/symfony-messenger-cloudevents)[ Packagist](https://packagist.org/packages/stegeman/symfony-messenger-cloud-events)[ RSS](/packages/stegeman-symfony-messenger-cloud-events/feed)WikiDiscussions main Synced 3d ago

READMEChangelogDependencies (27)Versions (19)Used By (0)

Cloudevents integation for Symfony Messenger
============================================

[](#cloudevents-integation-for-symfony-messenger)

Install
-------

[](#install)

`composer require stegeman/symfony-messenger-cloud-events`

Enable the bundle in your kernel:

*bundles.php*

```
return [
    ...
    Stegeman\Messenger\CloudEvents\CloudEventsBundle::class => ['all' => true],
    ...
];

```

Configuration
-------------

[](#configuration)

Configure the correct serializer for your transport:

```
transports:
    async:
        ...
        serializer: 'Stegeman\Messenger\CloudEvents\Serializer\CloudEventsSerializer'
    ...

```

To prevent your messages will be mapped to a PHP namespace each message must be named and matched with a message. This can be done by adding name -> class mapping to your configuration (config/packages/cloud\_events.yaml) :

```
cloud_events:
  registry:
    - name: "test-event"
      className: "App\\Domain\\Event\\TestEvent"

```

Now it is known which name to map to which class. This is necessary for both serializing as deserializing.

This is all that is needed to get started.

All set, go!

Override services
-----------------

[](#override-services)

It is possible to override the normalizer service. This can be done by adding the following to your configuration (config/packages/cloud\_events.yaml):

```
    cloud_events:
      ...
      normalizer_service_id: name.of.your.own.normalizer.service

```

###  Health Score

50

—

FairBetter than 95% of packages

Maintenance99

Actively maintained with recent releases

Popularity19

Limited adoption so far

Community4

Small or concentrated contributor base

Maturity63

Established project with proven stability

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~20 days

Recently: every ~66 days

Total

18

Last Release

6d ago

Major Versions

0.0.14-ALPHA → 1.0-BETA2025-09-19

### Community

Maintainers

![](https://www.gravatar.com/avatar/5addc4732a11c93520e74a69976027d57bbc3d38ccdc7368af44e6b9fab3a4c5?d=identicon)[stegeman](/maintainers/stegeman)

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/stegeman-symfony-messenger-cloud-events/health.svg)

```
[![Health](https://phpackages.com/badges/stegeman-symfony-messenger-cloud-events/health.svg)](https://phpackages.com/packages/stegeman-symfony-messenger-cloud-events)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)