Weave Code
Plus Laravel Package
slimkit/plus
SlimKit Plus is an open-source Laravel social networking platform for building community apps. It provides user profiles, activity feeds, follows, comments, likes, notifications, and APIs, plus a modular, extensible foundation for PHP developers launching feature-rich social communities.
💝The Plus (ThinkSNS+) is a powerful, easy-to-develop social system built with Laravel.
Frequently asked questions about Plus
- Is slimkit/plus a Composer package I can install into an existing Laravel application?
- No. SlimKit Plus, also known as ThinkSNS+, is a complete Laravel social application monolith rather than a reusable Composer library. It ships users, feeds, comments, likes, notifications, admin tooling, and APIs as a full system. Adopting it typically means forking the repository and owning the code, not running composer require. If you expect a headless, composable package or drop-in module, it is a poor fit.
- Which Laravel and PHP versions does SlimKit Plus support?
- You must verify this directly in the repository's composer.json and CI configuration before planning anything. The last release was in November 2020, so expect older PHP 7.x-era constraints and older Laravel constraints rather than compatibility with Laravel 10, 11, or 12. Do not assume modern Laravel support without testing. Budget for upgrade work if your application runs a current Laravel version.
- What license does slimkit/plus use, and can I use it commercially?
- The repository is flagged with a NOASSERTION license, which means the actual terms and redistribution obligations are unclear from automated metadata. Treat this as a legal gate before any production use. Review the LICENSE files and source headers with legal counsel, and clarify obligations for forking, modifying, and redistributing. Do not start customization until the license question is resolved.
- What infrastructure and services does SlimKit Plus require to run?
- Plan for a standard but non-trivial Laravel stack: MySQL, Redis, queue workers, and filesystem or object storage. The application also assumes scheduled tasks, migrations, and seeders, and may depend on external services for search, SMS, or payments. Inventory these requirements during a time-boxed spike deploy. Missing queue or storage configuration will surface quickly as broken feeds, notifications, or uploads.
- Is SlimKit Plus production-ready and actively maintained?
- It is a substantial historical codebase, but the last release in 2020 signals an aging dependency chain and weak current strategic viability. Community support is likely thin, and there is no evidence of ongoing security patching or vendor-backed maintenance. Treat it as a fork you must own, patch, and upgrade yourself. Production adoption is multi-month work, not a low-touch dependency decision.
- How do I install and deploy SlimKit Plus?
- The practical path is to fork the repository into an internal source control system, pin all dependency versions, and containerize the application. Then run migrations and seeders against a disposable database and provision Redis, queue workers, and storage in a spike environment. Do not deploy to production before completing a license review, dependency audit, and upgrade plan. Deployment is code-level ownership rather than package management.
- Can I use SlimKit Plus as a headless API or replace its authentication with my own identity provider?
- SlimKit Plus exposes APIs, but it is not designed as a clean headless backend, so expect coupling between its native auth, user model, and social features. Replacing authentication with an enterprise IdP is possible but requires code-level changes and careful integration through APIs or events rather than shared database coupling. Document the API contract and data export path before committing. Test auth replacement early because it affects users, permissions, and notifications.
- Does SlimKit Plus have tests and CI, and how should I evaluate its security?
- Test coverage and CI status are unknown from the package metadata, so inspect the repository workflows and test suite before relying on them. Run dependency and container scanning immediately, and generate an SBOM for the fork. The 2020 release date implies unknown CVE exposure in its PHP and Laravel dependency chain. Do not assume patches exist for known vulnerabilities.
- What are the alternatives if I only need social features like feeds, follows, and notifications?
- If a full social suite is not core to your product, use SlimKit Plus as a reference architecture rather than a production dependency. For narrower needs, evaluate smaller Laravel packages for notifications, activity feeds, or follow graphs, or build the specific modules you need. A composable approach avoids inheriting an aging monolith and its license uncertainty. The main reason to adopt Plus is that you want the complete social system and accept long-term fork ownership.
- How does SlimKit Plus scale, and what are the main operational risks?
- Standard Laravel scaling patterns apply: caching, queue workers, read replicas, object storage with a CDN, and search offload. Watch feed fan-out, notification queue backlogs, and database hotspots, and load-test before any pilot. The larger risks are organizational: abandoned upstream code, license challenges, unpatched CVEs, PHP or Laravel incompatibility, and failed upgrades. Mitigate with a named fork owner, pinned images, backups, and a rebuild escape hatch.
Weaver
How can I help you explore Laravel packages today?