gimm3fuel/easylap-server

This is a usable but very new package with solid basic packaging: it has an Apache-2.0 license, a README, tests, a complete 36-file source tree, minimal dependencies, no install-time lifecycle scripts, and no deprecation or archival indication. However, the release history is only a few hours old with two releases, and repository activity shows no commits or active maintainers in the last three months; this may reflect the package's newness, but it leaves maintenance and abandonment risk largely unproven. The repository also has no security policy or security scanning, and no release automation or workflow evidence was collected. It is reasonable for cautious evaluation or controlled use, but dependency adoption should wait for demonstrated ongoing maintenance and additional releases.

Latest v1.0.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational backing signal to offset the very small observed maintenance base.

Release history

The package is extremely new: it has only two releases and was first published earlier the same day, so there is little evidence of release maturity or sustained maintenance.

Repo commit activity

No commits and no active maintainers were observed in the last three months. Because the repository is newly created, this is partly explained by the package age, but ongoing maintenance capacity remains unproven.

Repo tooling

Composer is used as a build tool, but no security scanning tool is configured; the build setup is present while security-maintenance tooling is limited.

Security policy

The repository has no security policy. For a package that handles USB devices and network services, this is a transparency and vulnerability-reporting gap.