Common helpers and classes for ICanBoogie
68%
Total Score
75
100
88
50
The package has existed since March 2014 and has nine releases, but it has had no release in about 22 months and none in the last 12 months. This indicates slowing maintenance, though the package is mature rather than newly abandoned.
There were no commits and no active maintainers in the last three months. Combined with the absence of releases for about 22 months, this is a meaningful maintenance concern.
The repository uses Composer and Make for build-related work, but no security scanning tools were detected. That is a modest security-process gap rather than evidence that the package is unsafe.
The repository has no security policy. For a maintained shared library this reduces transparency about vulnerability reporting, though other repository documentation and tests provide some compensating structure.
All three workflows were analyzed with no dangerous triggers, untrusted checkouts, script injections, or audit findings. However, all eight action references are unpinned, leaving workflow dependencies exposed to upstream changes.
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.