imedge/influxdb-streamer

Its MIT license and organization-owned repository provide clear ownership and reuse terms. The 14-character README and completely unpinned CI references reduce confidence for a library, while no recent activity makes long-term maintenance uncertain.

Latest v0.4.0

Packagist

55%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes tests, which is a positive, but its README is only 14 characters and provides essentially no consumer guidance. The absence of a changelog is normal packaging practice and is not a concern here.

Release history

The package has had no releases in the last 12 months, and its latest release was about two years ago. This is a substantial maintenance concern despite four total releases since July 2024.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but current maintenance activity is absent.

Repo tooling

Composer build tooling is present, supporting a defined build process, but no security-scanning tooling was detected. The build tooling partly offsets the missing security automation.

Security policy

The linked repository has no security policy, leaving vulnerability-reporting expectations and handling procedures undocumented. This is a transparency gap, though it is not evidence of unsafe code by itself.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Thomas Gelf

Direct Dependencies

Dependency	Last Release	Score
psr/log Version ^3.0\|^1.0	—	—
amphp/redis Version ^2	—	—
imedge/json Version >=0.1	—	—
ramsey/uuid Version ^4	—	—
imedge/metrics Version >=0.1	—	—