franzliedke/studio
A workbench for developing Composer packages. observed · 2026-08-28
Health v2 · maintenance only
23/100
- Activity 0
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4253
- days_rel: n/a
- days_push: 864
- n_releases_24m: 0
Adoption not part of the score
1137 stars · 76 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A Composer plugin and CLI tool that lets PHP developers work on their own Composer packages while using them in an application. It symlinks local package directories into the vendor directory via Composer path repositories, avoiding development inside vendor.
Use cases
- develop a composer package while using it in an app
- symlink local php packages instead of installing from packagist
- dogfood my library without editing composer.json
- avoid developing inside the vendor directory
- set up phpunit and autoload config for a package workbench
When to choose
- you maintain PHP libraries and want to test them in real applications while developing
- you want seamless local package loading without manually switching repositories
When to avoid
- you don't use Composer for dependency management
- your project only consumes third-party packages from Packagist
Facets
cli-tool · maturity maintenance
package-manager developer-tools cli developer-tools cli cross-platform php composer php-packages symlink path-repositories local-development dogfooding command-line php
1 source
- readme: https://github.com/franzliedke/studio · fetched 2026-08-28 · 53d659897634
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| franzliedke/studio | main | 23 |
For agents
markdown · JSON · MCP: product_card(name="franzliedke/studio")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem