Shaark Laravel Package

Product Decisions This Supports

• Build vs. buy (self-host vs. SaaS): Shaark is a self-hosted Laravel application for bookmarks, link archiving, notes, and read-it-later workflows — not a composer require library. This release is relevant to a "self-host an internal Pocket/Pinboard alternative" decision rather than a dependency decision.
• Multi-user readiness: The fix for creating and deleting users (#77, #87) is the headline. If team/multi-tenant use was previously blocked by broken user lifecycle management, this release materially changes the viability of a shared internal deployment. Treat it as the gate for any pilot with more than one account.
• Roadmap fit for internal knowledge tooling: If the roadmap includes link archiving, research capture, or a lightweight internal knowledge base, this is a candidate to evaluate against Pinboard, Wallabag, Linkding, or a bespoke build. The archiving capability is the differentiator worth scoping.
• Operational risk assessment: The jump to Laravel 6.20 signals the project is tracking a framework line that is end-of-life. That is a maintenance-cost input to the build-vs-buy model, not a feature.
• Onboarding/seed behavior: The default user email changing to [email protected] affects first-run and seeded admin expectations. Worth checking against any internal runbook or provisioning script before upgrading existing instances.

When to Consider This Package

Consider it when:

• You need a self-hosted, single-tenant or small-team bookmark/archive tool and are comfortable operating a Laravel app (PHP runtime, database, queue/scheduler for archiving).
• Multi-user support is now a requirement — this release is the first signal that user creation/deletion is trustworthy enough to pilot.
• You want data ownership and no per-seat SaaS cost, and archiving of link contents is a must-have.
• You have Laravel/PHP capacity on the team to patch, upgrade, and fork if upstream slows down.

Look elsewhere when:

• You need a reusable Composer package/library — this is an application; adopting it means deploying and maintaining it.
• You require supported framework versions (Laravel 10/11) or a vendor-backed security patch commitment. Laravel 6.x is EOL; staying on it is a standing risk.
• You need enterprise identity (SSO/SAML/SCIM), granular RBAC, audit logging, or compliance controls — none are evidenced here.
• You need frequent, predictable releases or commercial support; the release cadence and issue-driven fixes suggest a maintainer-side project.
• Your use case is single-user, low-stakes — lighter-weight tools may be less operational overhead.

How to Pitch It (Stakeholders)

For executives: Shaark is an open-source, self-hosted bookmark and link-archiving application built on Laravel. Release 1.2.44 fixes user creation and deletion, which is the blocker that previously made shared team use unreliable — so a multi-user internal pilot is now defensible. Cost is infrastructure and maintenance time, not licensing. The main caveat is that it runs on Laravel 6, which is past end-of-life, so we should frame this as a time-boxed pilot with an explicit maintenance owner, not a strategic platform commitment.

For engineering: This is an app to deploy and operate, not a dependency to install. The 1.2.44 changes are small but meaningful: user lifecycle bugs are resolved, default seeded email is now [email protected] (check provisioning scripts), and the framework is pinned to Laravel 6.20 — still EOL. Recommend evaluating the fork-and-upgrade cost to a supported Laravel version before committing, and validating the user create/delete paths in a staging environment since that is the newly fixed surface area.