The release is stable and has a matching repository with release notes. Its single release was published over 10 years ago, maintenance has stopped, and the package has no license; the self-dependency also needs explanation.
35%
Total Score
0
50
67
67
Neither the package nor its repository declares or contains a detectable license. Developers therefore lack clear permission to use and redistribute it.
Only one release exists, published over 10 years ago, with no releases in the last 12 months. This strongly indicates abandonment risk despite the package not being deprecated.
The repository has had no commits and no active maintainers in the last 3 months, consistent with the release history showing prolonged inactivity.
The package declares one runtime dependency on itself, which is unusual and may make installation or dependency resolution fail unless it is an intentional packaging arrangement.
The artifact and repository contain only README.md and composer.json, leaving no visible implementation files. This is a substantial transparency concern for a package presented as a dependency.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
cisvaibhav/composertest Version dev-master | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.