PHPackages                             sloanlance/composery - 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. [Utility &amp; Helpers](/categories/utility)
4. /
5. sloanlance/composery

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

sloanlance/composery
====================

Composery: A Composer wrapper to read its configuration from a YAML file, composer.yml.

15

Since Nov 3Pushed 8y ago1 watchersCompare

[ Source](https://github.com/sloanlance/composery)[ Packagist](https://packagist.org/packages/sloanlance/composery)[ RSS](/packages/sloanlance-composery/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependenciesVersions (1)Used By (0)

Composery
=========

[](#composery)

A Composer wrapper to read its configuration from a YAML file, composer.yml.

---

> > > ## ⚠️ Note:
> > >
> > > [](#️note)
> > >
> > >  *This package is still in the very early stages of development.*
> > >  *Don't be disappointed by its lack of substance.*

---

Why‽
----

[](#why)

- Comments can't be added to composer.json because JSON doesn't allow comments.
- YAML allows comments.
- Bidirectional conversion between YAML and JSON is easy and reliable. (Except for the loss of YAML comments.)
- If loss of fidelity between between YAML and JSON is a concern, fret not. YAML can contain JSON and *still* allow comments.
- The [igorw/composer-yaml](https://github.com/igorw/composer-yaml) project good, but it only converts composer.yml to composer.json. It doesn't run Composer using the new composer.json file, though.
- In contrast, Composery will:
    - Convert composer.yml to composer.json.
    - Run composer using the new composer.json.
    - By default, delete composer.json before exiting.
    - Optionally keep composer.json when exiting, which is useful for debugging or distribution.

###  Health Score

20

—

LowBetter than 14% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity5

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity41

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

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.

### Community

Maintainers

![](https://www.gravatar.com/avatar/0f97296d4bb8e625c7e0da52a298177bfc974604641bb9ce11ea8fa634a897ac?d=identicon)[sloanlance](/maintainers/sloanlance)

---

Top Contributors

[![sloanlance](https://avatars.githubusercontent.com/u/17595351?v=4)](https://github.com/sloanlance "sloanlance (10 commits)")

### Embed Badge

![Health badge](/badges/sloanlance-composery/health.svg)

```
[![Health](https://phpackages.com/badges/sloanlance-composery/health.svg)](https://phpackages.com/packages/sloanlance-composery)
```

###  Alternatives

[felixnagel/t3extblog

A record based blog extension for TYPO3 CMS. Easy to use and packed with features (incl. comments, subscriptions for comments and posts, Wordpress like subscription manager, reasonable email sending in FE and BE, GDPR ready, BE modules, Dashboard widgets, RSS, Sitemap, ...). Flexible and powerful!

3421.6k](/packages/felixnagel-t3extblog)

PHPackages © 2026

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