Its narrow scope and two runtime dependencies keep integration straightforward. The source has no recent activity or security policy, and the linked repository does not identify this package in its README, so future maintenance and ownership are uncertain.
52%
Total Score
50
100
75
75
The package has had only two releases, both published about 846 days ago, with no release in the last 12 months. This indicates inactive maintenance, although the stable 1.0.1 line may be sufficient for a small utility.
The repository recorded zero commits and zero active maintainers in the last three months, with the last push about 846 days ago. This is meaningful evidence of stalled maintenance.
The repository name does not match the package name, and its README does not mention the package. That raises uncertainty about whether the linked repository is the actual source, even though a name mismatch alone could be normal for a subpackage.
The repository uses Composer for its build and dependency tooling, which fits the package ecosystem. No security scanning tooling is present, leaving a modest transparency and maintenance gap.
The linked repository is not archived, so it remains available for inspection and possible maintenance. Its last push was about 846 days ago, which is consistent with the inactive release history.
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.