Create, read and edit .zip files with JavaScript http://stuartk.com/jszip
88%
Total Score
90
100
95
80
50
No build attestation, trusted publisher identity, or staged publishing is reported, leaving release provenance less transparent than it could be.
Only 2 commits were made in the last 3 months, indicating low recent development intensity. This is partly offset by the current release and active issue and pull-request handling, so it is a caution rather than a severe abandonment signal.
The repository uses TypeScript, Grunt, and npm scripts for builds, but reports no security-scanning tools; the build process is established while security-process visibility is limited.
No repository security policy was found, reducing transparency for vulnerability reporting and response expectations.
Both workflows lack top-level token permissions declarations. No top-level write permissions were detected, but explicit least-privilege configuration is absent.
| Title | Versions | Severity |
|---|---|---|
CVE-2022-48285 jszip is vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in versions 0.0.0 - 3.8.0. | 0.0.0 - 3.8.0 | High |
CVE-2021-23413 jszip is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in versions 3.0.0 - 3.7.0 and 0.0.0 - 2.7.0. | 0.0.0 - 2.7.03.0.0 - 3.7.0 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
lie Version ~3.3.0 | — | — |
pako Version ~1.0.2 | — | — |
setimmediate Version ^1.0.5 | — | — |
readable-stream Version ~2.3.6 | — | — |
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.