Clearfacts Laravel Sdk Laravel Package

Product Decisions This Supports

• Build vs. buy for accounting/ERP integration: This SDK wraps the ClearFacts API behind a Laravel-native interface, letting you evaluate "integrate ClearFacts" as a configuration task rather than a custom HTTP-client project. The v0.2.0 release keeps that bet cheap: the vendor (or maintainer) absorbs upstream API and transport churn on your behalf.
• Security posture as a roadmap input: v0.2.0 exists solely to move from Saloon 3 to Saloon 4 because of published security advisories on Saloon < 4. That converts a transitive dependency risk into a version bump you can take deliberately rather than discover during a penetration test or procurement review.
• Feature scoping: Because the package is still pre-1.0 (0.1.1 → 0.2.0), treat its surface as unstable. Plan integrations against the ClearFacts API capabilities you actually need (invoices, documents, bookkeeping sync) and assume the SDK's method signatures may move under you.
• Sourcing/vendor diligence: A first-time contributor landing a security-driven upgrade is a positive maintenance signal (responsive, reviewable, public PR history) — useful evidence when deciding whether this package is a dependency you can defend to a security or finance stakeholder.
• Sequencing: If you are mid-build on a ClearFacts integration, this release is a "schedule the bump now" item, not a "redesign" item. It does not change what the integration can do.

When to Consider This Package

Adopt when:

• You are building a Laravel/PHP product that must read from or write to ClearFacts (Belgian accounting/bookkeeping) and you would otherwise hand-roll an HTTP client, auth handling, and DTOs.
• You already use Saloon elsewhere in the stack — this release aligns the SDK with Saloon 4, so a mixed Saloon 3/4 dependency graph is the main thing to check before upgrading.
• You want a dependency whose maintenance is legible: small diff, public PR, advisory-driven rationale.
• You can pin a version and absorb pre-1.0 breakage — i.e., the integration is not on a frozen long-term-support branch.

Look elsewhere (or wrap it yourself) when:

• You need a contractual SLA, vendor support, or a deprecation policy — this is a community package at 0.x with a single security bump as its most recent release.
• Your app is pinned to Saloon 3 for other integrations; Saloon 4 is a major upgrade and the SDK now requires it, so adopting v0.2.0 may force a broader dependency migration.
• You only need one or two endpoints — a thin Saloon connector of your own may be less total risk than a dependency that can break on minor releases.
• You are not on Laravel, or you need a non-PHP client.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost dependency for connecting our Laravel product to ClearFacts accounting data instead of building and maintaining that integration in-house. The new release is a security fix — it upgrades the underlying HTTP library (Saloon) off a version with published vulnerabilities. No new features, no change to what the integration does. Cost: a routine dependency bump and a regression pass. Value: we stay off a flagged library version and we can point to an actively maintained, publicly reviewed dependency.

For engineering: v0.2.0 is a single change: Saloon 3 → Saloon 4, motivated by security advisories on Saloon < 4. Treat it as a major-version bump of a transitive dependency. Action items: (1) check whether anything else in the app pins Saloon 3 — if so, resolve that first; (2) verify whether the SDK exposes Saloon request/response types in its public surface, since those signatures may have shifted; (3) run the integration test suite against a ClearFacts sandbox; (4) pin to ^0.2.0 and note the package is pre-1.0, so minor releases may still break. No deprecations or removals are announced in this release.