The package is small and clearly documented, with tests, a matching repository, and a permissive license. Its long release gap and absent recent commit activity make future fixes uncertain, while workflow references are not pinned.
58%
Total Score
50
100
78
75
The registry namespace and repository are owned by the same individual account, which aligns ownership but does not provide organizational backing to offset the thin maintenance base.
The package has only 3 releases since October 2014, with no releases in the last 12 months and a median interval of about 3.5 years. This indicates slow maintenance and lowers confidence in timely fixes.
There were 0 commits and 0 active maintainers in the last 3 months. Combined with the last release being in 2021, this is evidence of a project that may no longer receive fixes.
The repository has 3 stars, 0 forks, and 1 watcher. This shows a very small user and contributor base, so it offers little supporting evidence of ongoing maintenance, though popularity alone is not decisive.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
bigwhoop/crc24 Version ^2 | — | — |
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.