gipfl/influxdb

The library has seen no release for nearly four years and no recent repository commits, so compatibility and maintenance support are uncertain. MIT licensing and organization backing help, but the empty README and lack of tests or security scanning leave limited evidence for dependable integration.

Latest v0.5.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes a README entry, but it has zero recorded content; the source repository has no tests or changelog. Missing tests and changelog are normal packaging practice, while an empty consumer-facing README is a minor transparency gap.

Release history

The latest release was nearly four years ago, with no releases in the last 12 months. This is a meaningful maintenance concern, though the package has seven releases and is not deprecated.

Repo commit activity

There were no commits and no active maintainers in the three months before collection. Combined with the old latest release, this is strong evidence of inactive maintenance.

Repo tooling

The repository uses Composer, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.

Security policy

No security policy was found in the repository, leaving vulnerability-reporting expectations unclear. This lowers transparency but is not severe on its own.