appserver-io/logserver

Consumers get a clear starting point, while the project structure remains easy to inspect. The absence of security scanning and a security policy adds a smaller transparency concern, but the long inactivity is the central issue.

Latest 0.1.1

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, with the latest on November 3, 2014 and none in the last 12 months. This indicates a long-abandoned release line despite the package not being formally deprecated.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push being more than 11 years ago. This is strong evidence of abandonment risk.

Repo popularity

The repository has zero stars and forks and three watchers. Popularity is only supporting evidence, but these very low adoption signals provide no meaningful external confidence.

Repo tooling

Composer and Phing build tooling are present, showing a defined build process, but no security scanning tooling was detected. The tooling gap is a modest transparency concern rather than a severe risk.

Security policy

The repository has no security policy. For an old network-facing log server, this leaves vulnerability-reporting expectations unclear and modestly lowers transparency.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Johann Zelger

Tim Wagner

Direct Dependencies

Dependency	Last Release	Score
psr/log Version *	—	—
monolog/monolog Version 1.10.*	—	—
techdivision/http Version 0.1.*	—	—
techdivision/server Version 0.1.*	—	—
techdivision/webserver Version 0.2.*	—	—