The package is clearly identified, MIT-licensed, and has a matching repository with tests. Its small dependency surface and lack of install scripts reduce operational risk, but ongoing support cannot be relied on.
42%
Total Score
25
100
67
67
The package has only one release, published over five years ago, with no releases in the last 12 months. This is strong evidence of limited maintenance for a dependency that may need compatibility updates.
There were no commits and no active maintainers in the last three months, consistent with the package having received no update since its initial release. This materially increases abandonment risk.
The registry and repository are owned by the same individual account, so the package's source identity is consistent. There is no organization backing shown to provide redundancy if the maintainer stops responding.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these numbers provide no meaningful community support to offset the lack of maintenance.
Composer is used as a build tool, but no security scanning tools are present. The missing scanning is a hygiene gap rather than a standalone reason to reject the package.
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.