The one-person project has no recent development or releases, and its repository provides no security policy or scanning. A clear license, README, release notes, and minimal dependency footprint improve transparency but do not offset the long inactivity.
38%
Total Score
25
100
75
75
The latest release was about 4 years and 9 months ago, with no releases in the last 12 months. Only three releases exist, so ongoing maintenance is unlikely.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release gap and indicating inactive development.
The package has one registry maintainer. This is a narrow publishing base, and the available activity signals provide no evidence of a broader or active maintenance team.
Composer is used for build and dependency management, but no security scanning tools are present. This is a hygiene gap, though it is less significant than the project's inactivity.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in an API that accesses application data.
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.