The repository shows no commits or active maintainers in the last three months, and release history is sparse despite a recent release. Licensing, package identity, stable versioning, and the absence of install scripts are reassuring, but the project has no security scanning or security policy.
68%
Total Score
50
89
83
The repository recorded zero commits and zero active maintainers over the last three months. A recent push or release does not offset the lack of observed ongoing development.
A single registry maintainer is a thin publishing base, and the project is user-owned rather than organization-backed, leaving limited visible publishing redundancy.
The package has existed for about 3 years with five releases and one release in the last 12 months; the roughly 200-day median interval indicates sparse maintenance, though a recent release is compensating evidence.
There are no open issues or pull requests and no recent issue or pull-request activity; this provides little evidence of active community maintenance.
Composer build tooling is present, but no security scanning tools are configured, leaving a meaningful transparency and maintenance gap.
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.