rajatcomposer/mycomposer

The license information is inconsistent, and the linked repository does not clearly identify this package. Its artifact includes documentation, tests, and a changelog, but maintenance activity has stopped and the package has only one release.

Latest 1.0

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, published about 8 years ago, with no releases in the last 12 months. This is strong evidence of an abandoned dependency rather than an actively maintained one.

License

The manifest declares a proprietary license while the artifact contains a detected MIT license file, creating a material licensing mismatch. The presence of license files is positive, but it does not resolve which terms apply to this release.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. No stronger maintenance signal compensates for this inactivity.

Repo package mention

The repository name does not match the package name, and the README check found no package-name reference. That makes the repository-to-package relationship unclear, which reduces transparency.

Repo tooling

The repository uses Composer for builds, showing basic project tooling, but it has no reported security-scanning tools. This is a minor hygiene gap rather than the main adoption concern.