EN

Open source

Whatever keeps coming up across our projects, we write properly once and release as a package. Anyone is free to use the packages, and the source is on GitHub.

Why we publish

Written once, properly

Much of a web system is the same from one project to the next. The same validation or the same connection to an outside service would be written again each time, with the same chances to get it wrong. When we build that part once, with tests and documentation, the next project builds on it.

Public code also shows how we work. If you are considering having us build something, you can see how we write, test and document code before you commit to anything. Bug reports and their fixes are in the open as well.

packages released
7
downloads from Packagist
41

Commitments

Six commitments, for every package

A package is released only when it meets all six. The tools and the exact rules are in the guidelines.

  1. A named source

    When a package follows a law, a standard or an official specification, the documentation says which one, so you can check the rule yourself.

  2. Tested versions

    Every change runs the tests on every supported PHP and Laravel version. We only call a version supported when the tests pass on it.

  3. Automated checks

    Type errors and style issues are caught automatically in the pull request, before the code reaches the package.

  4. Predictable upgrades

    The version number tells you whether an upgrade needs changes in your own code, and the changelog records what changed in every release.

  5. In English and Hungarian

    Every README is written in both languages, with the same content.

  6. Safe by default

    When a setting touches a live system or handles sensitive data, it starts on the safe value.

Packages

What we have released

All packages

How you can help

  • If you find a bug, open an issue on the package’s GitHub page with the version and the steps that trigger it.
  • If you would like to fix it as well, send a pull request. New behaviour needs a test.
  • If a package works for you, a star on GitHub helps others find it.

Found a security issue?

Send it to info@intragile.eu rather than a public issue, where anyone could read it before the fix. We will reply within a few working days.

Building a custom system?

The same team also builds custom systems and keeps them running. Tell us in a few sentences what you are planning.

Get in touch