The one-person publishing setup and absent security policy reduce confidence. MIT licensing, stable versioning, and organization ownership provide useful context, but the project offers little supporting documentation.
43%
Total Score
50
75
75
The package is 621 days old but has had only three releases, all clustered within hours of its first publication, with no releases in the last 12 months. This is strong evidence of inactivity for a library dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating little visible maintenance capacity.
Only one registry account publishes the package, which is a modest resilience concern; the organization-owned repository partly compensates by providing project backing.
The artifact has no README, tests, or changelog. Missing tests and changelog are normal for published artifacts, but a missing README is a real consumer-documentation gap for middleware.
Composer build tooling is present, but no security scanning tools were detected, leaving a minor transparency and maintenance-hygiene 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.