Filanitics Laravel Package

Product Decisions This Supports

• Adoption decision: do not adopt. The v1.0.0 release note states this is “just a husk from the original” and explicitly advises against installing it. For a PM, this is a decisive exclude signal, not a candidate to pilot.
• Build vs. buy: Cannot support a build-vs-buy comparison. There is no usable artifact to benchmark against an internal build, a maintained open-source library, or a paid analytics vendor. Do not let it sit on a shortlist as a “free option” — it is not an option.
• Roadmap impact: Supports no roadmap items. It should not be attached to dashboard, reporting, or Filament panel work. Any roadmap line implying “analytics dashboards via this package” should be rewritten or the dependency removed from the plan.
• Use cases: None in production. The only defensible PM use is provenance triage — confirming whether this is a fork, mirror, placeholder, or name collision, and identifying the canonical upstream project to evaluate instead.
• Risk posture: Treat as a supply-chain and dependency-governance item, not a technical feature decision. An installable package whose own publisher disclaims it is exactly the failure mode a PM should escalate to platform/security rather than assign to an engineering spike.

When to Consider This Package

Consider it only in these narrow, non-product situations:

• You are investigating provenance: determining whether this is a legitimate fork or mirror of an original Filament analytics package, or checking for a typo-squat/name collision.
• You need to trace the original upstream because this release note is effectively a pointer to it.
• You are auditing an existing composer.json/composer.lock and need to document why this dependency must be removed or replaced.

Look elsewhere when:

• You need a working Laravel/Filament analytics dependency — the release itself says not to install this.
• You require maintenance, security patching, framework-version support, or an issue triage path — a husk release provides none of these.
• The original upstream package exists and is maintained — evaluate and adopt the source directly rather than routing through a hollow republish.
• You need something substantive for a build-vs-buy or vendor evaluation — there is nothing here to assess, benchmark, or pilot.
• You are planning a Filament dashboard feature — treat “Filanitics” as unavailability, not as a free head start.

How to Pitch It (Stakeholders)

For executives: This is not a usable component. The v1.0.0 release is explicitly a placeholder — the maintainer calls it a “husk from the original” and advises against installing it. Recommendation: exclude it from evaluation, do not budget engineering time for it, and continue with alternatives (a maintained upstream package, an internal build, or a vendor analytics product). No product investment is warranted.

For engineering: Do not add this to composer.json and do not install it in any environment, including sandboxes, without a provenance check. Treat the release as a marker, not a deliverable. Redirect anyone who surfaced it to the original upstream repository and verify licensing, maintenance activity, and security history there before considering adoption. If it already appears in a lockfile, flag it for removal or replacement in the next dependency cleanup and record the decision in the dependency register so the evaluation is not repeated.