The package has a clear MIT license, repository tests, and a matching source tree. Its workflows have no dangerous findings, though security scanning and a security policy are absent.
43%
Total Score
50
100
78
75
The registry namespace and repository are owned by the same individual account, so the source identity is consistent. There is no organization backing shown to compensate for the thin maintenance base.
The latest release was published nearly five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the 66-release history.
There were no commits and no active maintainers during the last three months. Combined with the old last push, this indicates that maintenance has effectively stopped.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no external adoption signal to offset the maintenance concerns.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.