jrbecart/laravel-influxdb

Release historydanger

The latest release was published about five years ago, and there have been no releases in the last 12 months. This strongly raises abandonment and compatibility risk despite the package having eight releases overall.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the last release being about five years ago, this is strong evidence of abandonment risk.

Dependency profilecaution

The package has only two runtime dependencies and no development dependencies, keeping its dependency surface small. The lack of development dependencies also provides little evidence of a maintained test or development workflow.

Repo popularitycaution

The repository has zero stars, forks, and watchers, offering no supporting evidence of adoption or community visibility. Popularity is not required for health, but this provides no compensation for the inactivity.

Repo toolingcaution

The repository uses Composer, confirming basic package tooling, but has no security-scanning tools. This is a transparency and maintenance gap, though it is less serious than the absence of recent development activity.