It has a clear README, tests, MIT licensing, release notes, and only one runtime dependency. The single-contributor project has little recent activity, no security tooling, and uses three unpinned workflow actions.
62%
Total Score
50
100
88
83
Only one registry account has publish access. For this individually owned repository that is consistent with the project backing, but it leaves limited visible publishing redundancy.
The package has only two releases, with the latest in November 2023 and none in nearly three years. That is a meaningful maintenance concern, though the package is small and its latest release includes documented changes.
There were no commits and no active maintainers in the past three months, consistent with the long gap since the last release. This reduces confidence that issues or compatibility needs will be addressed promptly.
Composer build tooling is present, but no security scanning tools were detected. For a small library this is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. That provides no stated process for reporting or handling vulnerabilities, although the package’s small scope limits the severity of this documentation gap.
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.