The repository has no security policy, and all three workflow actions are unpinned. A recent release, broad tests, a clear license, and read-only workflow permissions provide useful reassurance.
67%
Total Score
50
100
94
75
The package and repository are owned by the same individual, so ownership is consistent. Individual ownership does not provide the redundancy of an organization-backed maintainer team.
The repository recorded zero commits and zero active maintainers in the last three months. The recent release is a compensating sign, but the lack of ongoing source activity raises maintenance risk.
There are eight open issues but no issues or pull requests were opened or closed in the last month. This suggests limited current interaction, though it is not conclusive by itself.
Composer build tooling is present, but no security scanning tools are configured. For a maintained library, the missing security automation is a modest transparency and maintenance gap.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for developers adopting the library.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.