- Is devcode-it/openstamanager a Laravel package?
- No. Despite the Composer package name, OpenSTAManager is an application-scale PHP/MySQL management suite, not a composable Laravel library. The release spans admin configuration, plugins, PDF generation, OAuth2, a REST API, Docker builds, and import pipelines. Integration is effectively whole-application adoption rather than dropping a package into an existing Laravel app.
- Can I install devcode-it/openstamanager with Composer inside a Laravel application?
- You should not treat it as a normal Composer dependency for a Laravel app. The codebase includes legacy procedural entry points such as view.php, editor.php, ajax_select.php, and oauth2.php that sit outside Laravel routing, middleware, and authorization. Plan for standalone deployment or full application adoption instead of package-style integration.
- What PHP and Laravel versions does OpenSTAManager support?
- The provided release context points to PHP 8.x with an explicit compatibility fix for older fputcsv escape behavior, suggesting active PHP upgrade maintenance. Laravel version support is not applicable in the usual package sense because this is not a Laravel library. Confirm the supported PHP, database, and web server matrix against the project documentation before rollout.
- What modules are included in OpenSTAManager?
- OpenSTAManager includes modules for invoicing, quotes, orders, inventory, accounting, interventions, CRM, reporting, customer and supplier records, and sales and purchase documents. It also covers Italian fiscal workflows and tax compliance, including electronic invoicing. It is aimed at Italian small businesses, freelancers, and technical assistance operations.
- Is OpenSTAManager 2.11.1-beta safe to use in production?
- No. The release header explicitly states it must not be used in production environments, even though it contains many important security fixes. It also includes roughly 35 functional fixes across permissions, mail, invoicing, contracts, imports, and calendar behavior, which raises regression risk. Wait for a stable 2.11.x release or a security backport before production planning.
- How do I mitigate the known security issues in OpenSTAManager before upgrading?
- Interim mitigation includes blocking legacy .php endpoints at the web server, adding WAF rules, disabling the Configuration Wizard, and restricting settings and API routes. Review outbound HTTP egress from the application tier because mPDF-based PDF generation and the stored SSRF fix affect network policy. Treat earlier builds as compromised-until-proven-otherwise, especially given the unauthenticated RCE and Settings API key disclosure reports.
- Does OpenSTAManager support Italian electronic invoicing and tax compliance?
- Yes. OpenSTAManager is built for Italian small businesses and freelancers and includes Italian fiscal workflows, electronic invoicing, and tax compliance features. It also supports related accounting, sales, purchase, and inventory processes. Confirm current fiscal requirements and import pipelines against the specific release you deploy.
- Does OpenSTAManager work with MariaDB as well as MySQL?
- The release includes a MariaDB-specific query compatibility fix for the Articles view, so MariaDB is at least partially addressed. MySQL is the primary database in the described stack. Do not assume full MariaDB parity with MySQL; verify critical workflows on your chosen database before deployment.
- Can I deploy OpenSTAManager with Docker?
- Yes, the release includes a Docker image build fix, so container-based deployment is part of the project. Because deployment artifacts changed, revalidate existing container rollouts rather than assuming the previous image behavior. Also review network policy for outbound HTTP from the application tier due to PDF generation and related SSRF concerns.
- What alternatives or maintenance considerations exist for OpenSTAManager?
- If you need a composable Laravel invoicing or ERP library, OpenSTAManager is not a good fit because it is a full self-hosted application. For maintenance, ask whether a stable 2.11.x or 2.10.x security backport exists, whether advisories or CVEs were assigned, and what the support window and security-response commitment are. Those answers should be resolved before committing to the beta line.