- Can I use kch/pcc-3-deklaracja-bundle in a Laravel application?
- It is packaged as a Symfony bundle, not a Laravel package with a service provider. There is no native Laravel integration described, so do not expect composer require and auto-discovery to wire it up cleanly. Treat it as a reference implementation and plan to extract or rewrite the declaration logic inside your Laravel app.
- Does this package support the current PCC-3(5) v1-0E declaration version?
- The v5.1.0 release note states support for PCC-3(5) v1-0E, which is a positive signal. However, a one-line release note is not validation against the official schema or acceptance criteria. Confirm that this is the current official version and test the generated output before relying on it for filing.
- How do I install kch/pcc-3-deklaracja-bundle with Composer?
- The package is a Symfony bundle, so its installation and configuration assumptions are Symfony-oriented. In a Laravel application there is no documented service provider or configuration path, and PHP/Symfony constraints are unknown. Audit dependencies and packaging first, and budget for extraction or rewrite rather than a direct install.
- Is this package maintained and safe for production tax filings?
- A v5.1.0 release exists after long dormancy, so the archived-since-2017 characterization no longer holds literally. But a single release does not prove active maintenance, support cadence, or production adoption, and the project still shows zero stars and zero dependents. Tax correctness remains the critical risk, so do not use it in production without a full audit and output validation.
- What output format does the bundle generate for PCC-3 declarations?
- The overview says it builds declaration data with typed models and renders submission-ready output. It does not clearly state whether the artifact is official XML, PDF, or an internal array. That distinction determines how much logic is salvageable, so inspect the output before planning integration.
- Can I use this Symfony bundle with Laravel 10 or Laravel 11?
- Likely not cleanly, because the package is still described as a Symfony bundle and no Laravel support is mentioned. PHP and Symfony version constraints are unknown and may conflict with a current Laravel stack. Assume incompatibility at the packaging layer until v5.1.0 is audited.
- What are alternatives to using a Symfony bundle for PCC-3 in Laravel?
- Rewrite the declaration model directly inside a Laravel service or Artisan command and validate it against the current PCC-3(5) v1-0E schema. If the bundle contains meaningful tax-rule logic, extract that logic into a standalone class, strip Symfony coupling, and wrap it in a Laravel service provider behind an interface. The end state should be first-party code you own unless the package proves modern packaging tests and sustained support.
- How should I test PCC-3 declaration output before filing?
- Validate generated declarations against the official PCC-3(5) v1-0E schema and, where possible, compare against accepted submissions. Unit-test tax calculations, parties, and item data independently of the package. Do not rely solely on the bundle's own tests, and include accountant or domain-expert review because incorrect declarations carry legal and fiscal consequences.
- Does kch/pcc-3-deklaracja-bundle handle tax calculations and parties and items?
- The overview mentions reusable building blocks for items, parties, and tax calculations, so the package appears to model more than raw templating. The actual scope is still unclear: it could be thin formatting or genuine tax-rule logic worth preserving. Audit the code to decide whether to extract logic or rewrite it.
- Why is this package risky to add as a Composer dependency in Laravel?
- The main risks are Symfony packaging, unknown modern PHP and Symfony constraints, zero adoption signals, and release opacity. Most importantly, tax correctness is unverified, and incorrect PCC-3 output has legal and fiscal consequences. Use v5.1.0 as a reference implementation and keep the final integration as first-party code unless the audit proves modern packaging, tests, and maintainer support.