sting_bo/mengine

Clear MIT licensing, a usable README, and a small dependency set make the package straightforward to inspect and integrate. It also lacks tests and security scanning, increasing maintenance uncertainty.

Latest v1.0

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 2 years and 9 months ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last 3 months, consistent with the package's long release gap and indicating no visible ongoing maintenance.

Repo tooling

Composer is used for the build, but no security scanning tools were detected. The missing scanning is a maintenance and hygiene gap, though not evidence that the release is unsafe by itself.

Repository archived

The repository is not archived, which preserves a path for maintenance, but its last push was about 2 years and 9 months ago and does not offset the inactivity shown by release and commit history.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package used in application infrastructure.