The small codebase is clearly packaged, licensed, documented, and backed by repository tests. Its only release and no commits for about three years leave maintenance and compatibility uncertain.
58%
Total Score
50
100
86
83
The registry package and repository are both owned by the same individual account. This is consistent ownership, but it does not provide the redundancy of organization backing.
This is the package's only release, published about three years ago, with no releases in the last 12 months. That limited history makes ongoing maintenance and compatibility less certain.
The repository recorded no commits and no active maintainers in the last three months, while its last push was about three years ago. For a small library this may reflect stability, but it still provides weak evidence of current maintenance.
The repository uses Make and Composer for build tasks, but no security scanning tools were detected. The build tooling is a positive; the missing scanning is a minor transparency gap for this small package.
No repository security policy was found. That is a modest transparency gap, though the package's small scope and lack of detected workflow exposure limit its weight.
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.