The package has a clear MIT license, no runtime dependencies, tests, and a repository that matches its package name. Its last release and repository push were about three years ago, with no recent commits or issue activity; the missing security policy is a smaller transparency gap.
62%
Total Score
67
100
89
83
The package has existed since 2014 with 29 releases, but it has had no release in the last three years, which lowers confidence in ongoing maintenance.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push being about three years ago and raising abandonment risk.
There are no open issues or pull requests and no activity in the last month. This is consistent with a quiet project but provides no evidence of active support.
Composer is used for the build, but no security scanning tool is present. The missing scanning is a modest repository-hygiene gap, not evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a minor transparency concern for a package with no runtime dependencies.
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.