Clear licensing, documentation, and release notes make adoption straightforward. The small maintainer base and lack of a security policy reduce long-term confidence.
68%
Total Score
50
100
81
75
Only one registry maintainer is listed. That is consistent with a small user-owned project, but it creates limited publishing redundancy and raises continuity risk if the maintainer becomes unavailable.
The package has eight releases since October 2023, but no releases in the last 12 months and its latest release was about 13 months ago, indicating a currently quiet maintenance cadence.
There were no commits and no active maintainers in the last three months. Combined with the absence of releases in the last 12 months, this points to reduced recent maintenance activity.
The repository uses Composer for builds, but no security scanning tool was detected. This is a modest transparency and hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented reporting or response process for vulnerabilities and lowering maintenance transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
srwiez/thumbhash Version ^1.2 | — | — |
composer/installers Version ^1.0 | — | — |
kornrunner/blurhash Version ^1.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.