Site logo

// DEV1 Labs

Open Source We Publish and Keep Maintained

Labs is where our public packages live. They are not demos: they are versioned, released, and maintained in the open. Read the CI configuration and the release history — that is the clearest evidence we can give of how we build software meant to last.

View PackagesTalk about an idea
Published packages
4
CI coverage gate
≥80%
License
MIT

Every release goes through

  1. 1CI enforces a minimum of 80% test coverage — below that, the release is blocked.
  2. 2The version tag is cut from the CHANGELOG, so the changelog cannot drift from the release.
  3. 3A GitHub Release is published, and the registry is notified automatically.

// Packages

What We Publish and Maintain

Open source we ship, version, and keep working. Every package below is public, MIT-licensed, and installable today — the code, the tests, and the release history are all open to inspection.

PHP · Packagist

dev1/notify-core

Maintained

Driver-agnostic notification core with a Firebase Cloud Messaging HTTP v1 driver. Built against PSR-18 and PSR-17 so it is genuinely decoupled from any single HTTP client, rather than wrapping one.

View on Packagist Read the source
PHP · PSR-18/17
MIT

PHP · Packagist

dev1/notify-laravel

Maintained

Laravel adapter for notify-core, tested across a broad compatibility matrix: Laravel 8 through 13, on PHP 7.4 through 8.5.

View on Packagist Read the source
PHP · Laravel 8–13
MIT

Dart · pub.dev

editorjs_flutter

Maintained

Viewer and editor for the EditorJS document schema in Flutter, structured with Clean Architecture. Published under the verified publisher labs.dev1.mx, and open to external contributors.

View on pub.dev Read the source
Dart · Flutter
Verified publisher

Also published

PHP · Packagist

rzerostern/payu

Maintained

Unofficial wrapper for the PayU LATAM API. Published under an earlier namespace that stays put: there are live installs depending on it.

View on Packagist Read the source
PHP

// Why This Matters

The Argument Is How We Build

We are not going to argue from install counts — you can check those yourself in two clicks. What is worth your attention is the engineering discipline behind these packages, because it is the same discipline we bring to a system you will depend on for years.

  • CI enforces a coverage floor of 80%. It blocks the release rather than warning about it.
  • Releases are fully automated: the tag comes from the CHANGELOG, then a GitHub Release and the registry notification follow.
  • Genuinely agnostic design. notify-core targets PSR-18 and PSR-17 interfaces instead of coupling to one HTTP client.
  • MIT licensed, published under a verified publisher, and tested across broad compatibility matrices.

And when AI writes part of it?

We publish the rules we hold ourselves to — what AI agents may touch, what always needs a human, and who carries responsibility for the result.

Read our AI contributions policy

01.

Coverage Gate

A pull request that drops coverage below 80% does not release. The threshold is enforced in CI, not by convention.

02.

Automated Release

Tag cut from the CHANGELOG, GitHub Release published, registry notified — no manual step to forget.

03.

No Lock-In

Built against PSR interfaces, so you bring your own HTTP client instead of inheriting ours.

04.

Wide Support

Compatibility matrices spanning Laravel 8–13 and PHP 7.4–8.5, so upgrades stay on your schedule.