Weave Code
Vantage Laravel Package
storviaio/vantage
Vantage is a Laravel package for defining and managing database views in code. It offers a fluent schema-builder-style API, migrations, and Eloquent-friendly querying so you can version views alongside your app and keep complex SQL organized.
Vantage : Advanced Laravel Queue Monitoring & Insights package
Frequently asked questions about Vantage
- How do I install storviaio/vantage in a Laravel application?
- Install it with Composer and let Laravel's package auto-discovery register the service provider; no sidecar or runtime agent is required. The release assessment recommends pinning an exact version rather than a caret range because the package is pre-1.0. Install first with the optional REST/JSON API left disabled and confirm existing routes and config are unaffected. Then publish any config or migration files the package ships and re-check behaviour in a non-production environment.
- Which Laravel and PHP versions does Vantage support?
- The release notes do not publish an explicit support matrix, so check the composer.json constraints before committing to an upgrade path. The dev-dependency line (Larastan 3.x and PHPStan 2.x) implies the project's CI targets a recent PHP and Laravel matrix, but treat that as an implicit signal rather than a guarantee. Pin the package in a test application on your target PHP and Laravel versions and run your own suite against it.
- Is the Vantage REST/JSON API enabled by default?
- The API added in v0.1.25 is described as optional and additive, intended so that consumers who never enable it inherit no new attack surface or behavioural change. Whether turning it on requires publishing config or running migrations is not stated in the notes. Install with the API off, verify nothing changed, then enable it deliberately in staging before it ever reaches production.
- Does Vantage use Laravel Sanctum, Passport, or its own token auth for the API?
- The release notes only say Bearer token authentication and do not name Sanctum, Passport, or a custom implementation. That matters because token issuance, storage, hashing at rest, expiry, rotation, revocation, and scoping are application-level concerns a package can scaffold but cannot fully assume. Review the token code path before enabling the API and confirm it conforms to your existing authentication policy.
- What rate limits and throttling does the Vantage API apply by default?
- The supplied notes do not document default rate limits or throttling behaviour, so assume you must configure them yourself. Apply your application's standard throttle middleware to the Vantage routes and set per-token limits in line with your other APIs. Watch for burst traffic after enabling it, since a newly exposed authenticated endpoint is an easy target.
- Is v0.1.25 a drop-in upgrade from v0.1.24?
- The release notes do not state backward compatibility, though the only functional change (the optional API) is additive and the remainder is dev-dependency bumps for PHPStan, Larastan, Pint and related rules. Treat the upgrade as unverified: install it in a non-production environment, diff the published config and routes, and run your test suite. Because the package is pre-1.0, a patch release can still contain breaking changes.
- Can I safely use Vantage in production while it is still v0.1.x?
- Pre-1.0 versioning means nothing prevents a breaking change in a patch release, so adoption needs an exact pinned constraint and a diff review per bump rather than a caret range. The library itself is low-friction to integrate; the API capability is the moderate-risk part. If you ship it, enable the API only after the token lifecycle and authorization questions have been answered.
- Does Vantage overlap with Laravel Horizon, Telescope, or Sanctum?
- The release notes do not state the package's core capability, so ownership boundaries against existing tooling such as Sanctum/Passport, existing REST resources, and existing dashboards remain unverified. Map Vantage's actual feature set against what you already run before adopting it, particularly around authentication and monitoring overlap. Where it does overlap, keep one system of record rather than running both.
- Does the Vantage API enforce the same authorization rules as the rest of my app?
- That is not answered in the release notes, and a package-added auth path that diverges from your existing policy is the most likely source of a security finding. If the API serializes resources previously reachable only through authenticated server-rendered routes, the serialization contract becomes a security boundary. Do a field-level review of every response and confirm authorization parity with your existing UI surfaces.
- Who maintains Vantage and how active is the project?
- The contribution pattern in this release, one feature author plus Dependabot dev-dependency bumps, suggests a small maintainer base. Pre-1.0 versioning combined with thin maintainer coverage is the dominant long-term risk here, not code quality. Plan for it by pinning versions, keeping an upgrade runbook, and being ready to fork or vendor the package if maintenance stalls.
Weaver
How can I help you explore Laravel packages today?