- How do I install sepremex/filanitics in a Laravel application?
- You should not install it. The v1.0.0 release notes state the package is "just a husk from the original, no need to install from here," which is an explicit instruction from the maintainer not to adopt it. Even though the package name is installable via Composer, pulling it in would add a dependency its own publisher disowns. Close the evaluation and add the package name to your dependency denylist instead.
- Is Filanitics safe to use in production?
- No. Beyond the missing quality signals, the release note itself says the artifact is not the canonical implementation, so you cannot verify what was stripped, added, or left behind. A published, installable name that the legitimate maintainer tells you not to use is a supply-chain hazard, not just a maintenance concern. Treat it as blocking rather than as a risk to be mitigated with config.
- What does "just a husk from the original" mean in the Filanitics release notes?
- It means the code published under this Composer name is not the canonical implementation and the maintainer does not stand behind it. The statement implies the real package lives elsewhere, and this name was published without substantive content. Because there is no declared surface area such as service providers, facades, contracts, config files, or migrations, there is nothing to map against a Laravel service topology. Treat architectural fit as not applicable rather than unknown.
- Which Laravel and Filament versions does Filanitics support?
- There is no trustworthy version matrix. The package declares no Laravel or Lumen constraint, no PHP version floor, and no verifiable package discovery configuration, so you cannot infer compatibility from the name or from historical releases of the original. Do not assume backward compatibility with prior versions of the upstream package, because the release note implies structural divergence by design. Any Filament v2, v3, or v4 claim would be unverified.
- What are the alternatives to Filanitics for Filament analytics dashboards?
- Start by identifying the canonical upstream package this release is a husk of, then check whether that upstream is actively maintained and repoint to it with an explicit pinned constraint. If no maintained upstream exists, build the reporting surface with Filament's own dashboard widgets and chart widgets, which cover most metric and filter use cases without a third-party dependency. Laravel Pulse is a reasonable option for application-level performance metrics that need to sit outside the admin panel. Plan a functional replacement rather than a version bump.
- Is sepremex/filanitics still maintained?
- There is no evidence of active maintenance. Publishing a v1.0.0 whose only content is a do-not-use notice is a terminal-maintenance signal, not a roadmap. There is also no visible changelog history, supported version matrix, CI pipeline, or static analysis configuration to indicate ongoing work. Plan on the assumption that this name will never receive fixes.
- My composer.lock already references sepremex/filanitics. What should I do?
- Audit composer.json and composer.lock across every service to find the requiring party, whether direct or transitive, and open a remediation ticket. If it is a direct dependency, confirm the original package is still resolvable and maintained and repoint to it with a pinned constraint; if not, plan a functional replacement. If it is transitive, raise the issue with the intermediate package maintainer rather than vendoring or patching around it. The release note is effectively a disclosure that you are pinned to an artifact its publisher does not support.
- How do I block sepremex/filanitics from being installed via Composer?
- Add the package name to a deny list and enforce it in CI, for example with a Composer conflict entry in your root composer.json so resolution fails loudly rather than silently. Scan all composer.lock files for the name to confirm nothing in production currently resolves it. If Packagist has not flagged the package as abandoned, consider requesting that the flag or a security advisory be set. Notify platform and security owners so the denylist entry is not quietly removed later.
- Does Filanitics include tests, CI, or static analysis?
- There is no evidence of any quality gates. No tests, continuous integration configuration, static analysis baseline, or supported version matrix is documented, and the release note itself argues against spending effort to find out. Because the published artifact is self-described as a non-canonical husk, any test suite that did exist would not tell you anything about the code you actually depend on. Do not treat the absence of reported failures as a passing grade.
- Who owns the sepremex/filanitics Packagist name, and is that a risk?
- Provenance is unclear, which is the core problem. It is unknown whether the publisher of this package is the same identity as the original author or whether ownership of the name has transferred. A published, installable package name that the legitimate maintainer says not to use is a namespace-squatting and future-takeover hazard, because the name may be re-registered or hijacked later and Composer will resolve it without complaint. Confirm the Packagist release history, check whether v1.0.0 was the first release or a replacement of previously substantive versions, and check for an abandoned flag before making any dependency decision.