Weave Code
Iss Satellite Laravel Package
bildvitta/iss-satellite
Bildvitta ISS Satellite is a Laravel/PHP package that provides satellite-style integration helpers for your application, simplifying configuration and service wiring for ISS-related data and workflows with a lightweight, developer-friendly approach.
At a glance
Frequently asked questions about Iss Satellite
- What does bildvitta/iss-satellite do?
- It is a Laravel/PHP companion package from Bildvitta intended to plug into the ISS ecosystem with satellite modules, integrations, and helpers. In practice it most likely acts as a thin domain adapter for Brazilian ISS municipal service tax rules or a client for an internal ISS service. The README is scaffold text, so verify the actual behavior by reading the source before assuming anything.
- How do I install bildvitta/iss-satellite?
- Install it with composer require bildvitta/iss-satellite in a throwaway Laravel app first, not your main application. The package likely auto-discovers its service provider, but check for publishable config and any required environment variables. Pin an exact version rather than a caret constraint while you evaluate it.
- Which Laravel and PHP versions does bildvitta/iss-satellite support?
- That information is not dependable from package metadata, so open composer.json and inspect the illuminate/* and php constraints directly. Then run a compatibility spike against your exact Laravel and PHP matrix. Zero dependents means there is no third-party evidence it has run outside the author's stack.
- Is bildvitta/iss-satellite production ready?
- Treat it as unvetted third-party code: one vendor, one maintainer, zero stars, zero dependents, and a 20/100 technical score. The release metadata includes a future-dated tag, so verify the tag against the default branch before trusting it. If you adopt it, wrap it behind your own interface and keep it out of domain code.
- Does bildvitta/iss-satellite create database tables or migrations?
- The metadata does not say, and schema coupling is a material unknown. Inspect the source for migrations, Eloquent models, table or column assumptions, and seeders before installing in any app with a real database. If it ships migrations, review and own them rather than running them blindly.
- Does bildvitta/iss-satellite make external API calls?
- If the package is an ISS service client it may make outbound HTTP calls using your credentials, which adds latency, retry, and secret-management concerns. Search the source for Guzzle, Laravel's HTTP client, hardcoded endpoints, and timeout settings. Only the pure calculator form of this package is low-risk.
- Is the ISS tax calculation in iss-satellite jurisdiction-aware?
- Unknown. Tax logic that is hardcoded to a single municipality and unmaintained is a compliance liability, not a normal dependency. Ask Bildvitta for the source-of-truth specification and check whether rules are versioned or jurisdiction-aware. If not, reimplement the behavior in-house.
- Can I use bildvitta/iss-satellite outside Brazil?
- If you do not operate in Brazilian real estate or municipal service invoicing, domain fit is effectively zero and this package is not a candidate. It is a domain adapter, not general infrastructure, so there is little to reuse outside that context. Even inside that context it is only worth adopting behind your own abstraction.
- What are alternatives to bildvitta/iss-satellite?
- There is no documented ecosystem of alternatives around this package, so the realistic options are reimplementing the small surface in-house or wrapping the package behind a port. Given the compliance sensitivity of tax logic, reimplementation is often the cheaper long-term path. A one-to-two-day spike will usually tell you which is right.
- How do I keep bildvitta/iss-satellite secure and updated?
- Pin the exact version in composer.json, commit the lock file, and configure Renovate or Dependabot to require manual review for this package and its subtree. Because bus factor is one, plan for the vendor disappearing or abandoning semver. Keep your own tests around the wrapped contract so you can swap implementations later.
Weaver
How can I help you explore Laravel packages today?