didrive/service

The package is small and easy to inspect, but its licensing records conflict and the repository has no security scanning or policy. Its lone release and absent recent development leave little evidence of ongoing support.

Latest 0.0.1

Packagist

35%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, 0.0.1, published in December 2019, with no releases in the last 12 months. That is strong evidence of an unmaintained dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its only release. No compensating maintenance activity is present.

License

The manifest declares MIT while the artifact license file is detected as Apache-2.0; although a license file is present, the mismatch creates legal ambiguity for consumers.

Repo package mention

The repository name does not match the package name and its README does not mention the package, so ownership of the published artifact is not clearly established. This is a supply-chain transparency concern.

Repo tooling

Composer is used for the build, which is appropriate, but no security scanning tools are configured. This is a modest hygiene gap rather than evidence of abandonment by itself.