kasan/logger-package

MIT licensing, a substantial README, and no install-time scripts improve transparency and reduce installation surprises. There is no security policy or scanning, and the repository has no visible community activity, so future fixes and review capacity are uncertain.

Latest 1.2.1

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package was first released about 8 years ago, but its latest release was June 2018 and it has had no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the last push being about 8 years ago, this indicates that fixes are unlikely to arrive promptly.

Project backing

The repository is owned by a user account rather than an organization, and the registry namespace is also user-associated. This is not inherently unhealthy, but it provides limited visible institutional backing for a dormant project.

Repo popularity

The repository has 0 stars, 0 forks, and 1 watcher. Popularity is not required for a healthy small package, but these counters provide little evidence of external review or a broader support base.

Repo tooling

Composer is used as the build tool, but no security-scanning tooling is present. The build setup is appropriate, while the missing scanning reduces maintenance and review assurance.