Usable with caveats: the release is licensed, documented, reproducibly structured, and backed by a matching repository with recent release activity. However, the repository shows no commits or active maintainers in the last three months and lacks security scanning and a security policy.
74%
Total Score
75
100
89
80
The repository recorded zero commits and zero active maintainers during the last three months. This conflicts with the recent release and raises concern that maintenance may rely on infrequent release preparation rather than ongoing development.
The repository has zero stars, forks, and watchers, so there is no community adoption signal to compensate for the thin maintenance history. Low popularity alone is not disqualifying for a small specialized package.
Composer build tooling is present, but no security-scanning tools were detected. That is a maintenance and transparency gap for a package distributed to downstream consumers.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
Both analyzed workflows lack top-level token permissions, although none declares top-level write access and one uses job-level permissions. This is a workflow-hardening gap rather than evidence of unsafe behavior.
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.