Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Version Information Bundle Laravel Package

leaseweb/version-information-bundle

A Symfony bundle that gathers and exposes version information for your application and its Composer dependencies, making it easy to surface build/version metadata for monitoring, health checks, and deployment diagnostics.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Developer experience investment: Informs whether to fund small DX conveniences such as showing Git/SVN working-tree status while testing. This package is a dev-only Symfony Web Debug Toolbar extension, not a customer-facing capability.
  • Build vs. buy/adopt: Supports a “do not build custom” decision only for legacy Symfony apps already using the debug toolbar. For Laravel, treat it as a reference pattern, not an adoptable dependency.
  • Release hygiene roadmap: The underlying use case—spotting dirty working copies, uncommitted changes, or ambiguous build provenance—can justify lightweight CI checks or IDE tooling. The package itself is too old to anchor that roadmap.
  • Use cases: Local/staging debugging, onboarding engineers, preventing “works on my machine” confusion from uncommitted changes, and validating deploy artifacts. It has no product-facing feature value.
  • Portfolio risk: Archived since a 2016 release, 25 stars, 0 dependents, and Symfony-specific. PM recommendation: deprioritize; do not add to a Laravel dependency portfolio.

When to Consider This Package

  • Only when maintaining a legacy Symfony app already on the Web Debug Toolbar, with compatible PHP/Symfony versions, and you need quick dev-only status output with minimal implementation effort.
  • The team accepts archived, unsupported software; the dependency is pinned, dev-only, never exposed in production, and has an explicit removal path.
  • Look elsewhere for Laravel applications—this is not a Laravel package. Also avoid it for modern Symfony/PHP 8+, maintained-support requirements, production use, CI enforcement, security/compliance needs, or multi-repo/VCS workflows.
  • For Laravel teams, use native Git tooling, IDE integrations, CI dirty-tree checks, or a small dev-only helper instead.

How to Pitch It (Stakeholders)

  • Executives: A low-cost, dev-only convenience for legacy Symfony debugging. It has no customer impact, no revenue contribution, and is archived/unsupported. Do not treat it as a strategic investment or a Laravel solution.
  • Engineering: It surfaces Git/SVN status in the debug toolbar, which helps engineers notice uncommitted changes. But it is a stale Symfony bundle with zero dependents and no maintenance. Adopt only in an isolated legacy dev environment with a removal plan; otherwise replicate the minimal behavior or rely on IDE/CI tooling.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
se7enxweb/flysystem
lampwick/laravel
jeslage/statamic-emojis
micahdshackelford/rmap-laravel
draftsmaninc/draftsman
square-bit/laravel-volition
himito/laravel-mailman
htinlynn/genius-helper
maco-studios/hephaestus
elmogy/larafast
xeviant/laravel-paystack
gorilladash/laravel-website-sdk
martialbe/flysystem-oss
chondal/3312client
jeroen-g/flickr
opscale-co/nova-genbi
itsjustvita/laravel-retention
tequilarapido/trackit
gregsphotography/site-builder-filament
cabaoctavio/laravel-query-log