- Does Blogged support Laravel 9, 10, or 11?
- No. The last release was March 2020, targeting Laravel 6 and 7 with PHP 7.2 through 7.4, and the repository is archived with no maintainer. Expect dependency resolution failures or deprecation noise on Laravel 9, 10, or 11. Plan to fork it rather than install it as a dependency on a modern stack.
- How do I install binarytorch/blogged with Composer?
- Run composer require binarytorch/blogged on a Laravel 6 or 7 application running PHP 7.2 to 7.4, then publish the package config and migrations and run php artisan migrate. Views and config are publishable so you can customize them without editing vendor files. On newer framework versions the install will likely fail on version constraints, which is the practical ceiling of the package as a drop-in dependency.
- Is Blogged still maintained and safe to use in production?
- It is archived, has no active maintainer, and no CVE response path, so security fixes will not arrive upstream. Markdown rendering is an XSS surface, and an unmaintained 2020-era parser dependency raises the risk further unless you verify and enforce sanitization yourself. Treat it as a reference implementation to fork and audit, not a production dependency.
- Does Blogged sanitize Markdown HTML output to prevent XSS?
- That is not clearly documented, so assume nothing and verify before exposing rendered posts publicly. Check which parser and version it pins and whether raw HTML passes through, then add your own sanitization layer such as HTMLPurifier or a strict CommonMark configuration. Post authors and any user-submitted content should be treated as untrusted input.
- Can I customize Blogged routes, views, and configuration?
- The package ships publishable config, migrations, and views, so you can override templates and adjust settings without touching vendor code. Routes are registered by the service provider under its own namespace, and disabling or re-prefixing them depends on what the config exposes, so review the config file or fork the provider if needed. Anything beyond config-level changes means maintaining a fork.
- What authentication and authorization does the Blogged admin dashboard use?
- It integrates with Laravel built-in authentication and authorization, so it assumes a standard session guard and middleware-protected admin area in a Blade monolith. It is not designed for token guards, API-only apps, or headless admin front ends. Confirm the exact guard, gates, and policies in the source before mapping it onto a custom auth setup.
- How does Blogged handle featured images and media uploads?
- Posts support featured images and configurable fields, but media handling is not well documented and may be URL-based or tied to a local storage disk. If you need S3 or CDN-backed uploads, expect to add that yourself. Inspect the migration and model casts to see what the image column actually stores.
- Is Blogged a good fit for a headless or API-first Laravel app?
- No. It is built for the classic Laravel monolith with Eloquent, Blade views, and server-rendered pages, not for JSON APIs, Inertia or React admin panels, or a separate content service. Multi-tenant and multi-database setups are also a poor structural fit. In those architectures it will be fought rather than adopted.
- What database tables does Blogged create?
- The publishable migrations typically create posts, categories, tags, and comments tables along with the pivot tables for their relationships. Once published, that schema becomes yours, and migrating away from it later is real work. Review the migrations before running them so you know exactly what you are accepting into your application.
- Does Blogged have tests that run on modern PHPUnit?
- Test coverage is unclear and the suite dates from the 2020 PHPUnit era, so it may not run on current PHPUnit without changes. If you fork the package, budget time to modernize the tests before trusting the admin CRUD. Running the existing suite on your target PHP version is the fastest way to judge the fork cost.