fleetbase/vroom-api

Release historycaution

The package is 471 days old with four releases, including three in the last 12 months, but releases are roughly 150 days apart. This indicates modest rather than rapid maintenance.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention fleetbase/vroom-api. That creates a genuine risk that the package-to-source relationship is unclear, although the namespace and repository owner match.

Repo toolingcaution

The project uses Composer build tooling, but no security-scanning tools were detected. For a package containing backend and frontend code, that is a modest transparency and maintenance gap.

Security policycaution

The repository has no security policy. This leaves vulnerability reporting and response expectations undocumented, reducing project transparency.

Version stabilitycaution

Version 0.0.4 is not a stable-major release, so its pre-1.0 status leaves API stability less certain. It is not marked as a prerelease, which partly offsets that concern.