A pure javascript JPEG encoder and decoder
68%
Total Score
75
100
89
67
The package has 21 releases since 2014, but no registry release in over four years. That long release gap is a meaningful maintenance concern for a dependency, even with the repository still present.
There were no commits and no active maintainers in the measured three-month period. This indicates currently slow source development, although the recent repository push prevents treating it as clearly abandoned.
No build tools or security scanning tools were detected. This is a hygiene gap, but the small pure-JavaScript package and its test suite partly reduce the concern.
The repository has no security policy, reducing transparency about vulnerability reporting and maintenance expectations.
The single workflow was fully analyzed with no audit findings or untrusted triggers, but both action references are unpinned. That leaves a modest workflow reproducibility and supply-chain hygiene gap.
| Title | Versions | Severity |
|---|---|---|
CVE-2022-25851 jpeg-js is vulnerable to Loop with Unreachable Exit Condition ('Infinite Loop') in versions 0.0.0 - 0.4.4. | 0.0.0 - 0.4.4 | High |
CVE-2020-8175 jpeg-js is vulnerable to Uncontrolled Resource Consumption in versions 0.0.0 - 0.4.0. | 0.0.0 - 0.4.0 | Medium |
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.