symplify/package-builder
Helper utilities for building Symfony/PHP packages: lightweight DI and service configuration, parameter resolution, class and file helpers, and tooling-friendly conventions. Designed to reduce boilerplate when composing reusable packages and developer tools.
This package is archived and no longer maintained, making it unsuitable for any new product decisions. It historically aided DI container integration and console app development for Symfony/Nette but now poses significant risks (security vulnerabilities, compatibility issues, lack of support). Product managers should prioritize modern, actively maintained alternatives for DI/container solutions and avoid adopting this package for new features, roadmap planning, or "build vs buy" considerations. Its use would only apply to legacy maintenance scenarios where migration is temporarily infeasible.
Only consider this package if maintaining an existing legacy system that already depends on it and migration is blocked by critical constraints (e.g., time, budget, or technical debt). For all new projects, do not adopt it—its archived status means no security patches, bug fixes, or compatibility updates. Instead, evaluate actively maintained alternatives like Symfony’s built-in DI components, Laravel’s service container, or Nette’s modern DI tools. If your stack is Symfony/Nette-based, prioritize community-vetted, up-to-date packages with recent commits and active contributors.
To executives: "This package is archived and unsupported, meaning it no longer receives security updates or maintenance. Using it would introduce avoidable risks to our product’s stability, compliance, and scalability. We recommend investing in modern, actively maintained solutions to ensure long-term security and reduce technical debt—saving future costs and accelerating feature delivery."
To engineering: "Since this package is archived, adopting it would force us to maintain outdated code with no community support. We should phase it out immediately and replace it with current best practices (e.g., Symfony’s DI components or Laravel’s native tools). This eliminates future vulnerabilities, simplifies upgrades, and aligns with our commitment to maintainable, secure code."
How can I help you explore Laravel packages today?