← Home

@yarnpkg/libzip

npm Repository
13
Versions
BSD-2-Clause
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

daniel15bestandercpojerarcanisyarnbot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:lib/libzipAsync.js AI (source-diff): This is an Emscripten-compiled WASM wrapper for libzip. Long lines are inherent to Emscripten output; not obfuscation. Stable pattern for this package. ai
source-diff obfuscated-file:lib/libzipSync.js AI (source-diff): Same as libzipAsync.js — Emscripten WASM bundle for libzip. Long lines are expected from the Emscripten toolchain, not malicious obfuscation. ai
provenance publisher-changed AI (provenance): yarnbot is the official Yarn project automation account; publisher transition from arcanis to yarnbot is a documented org-level change, not a compromise. Stable for this package. ai
email-domain unclaimed-email:rome.tools AI (email-domain): Co-maintainer email using defunct rome.tools domain; primary publisher is arcanis (Yarn core maintainer) with strong track record. Risk of hijack affecting this package is low. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is in Emscripten-compiled WASM wrapper (libzipAsync.js); standard pattern for embedding WASM binaries, not a malicious payload indicator. ai
phantom-deps phantom-dep:@types/emscripten AI (phantom-deps): Expected phantom dep for a WASM/Emscripten-based package; @types/emscripten is a type-only dev dependency used by convention. ai
npm-metadata no-description AI (npm-metadata): Established Yarn Berry monorepo package; missing description is a known metadata gap, not a malicious signal. ai
bogus-package bogus-package AI (bogus-package): Well-known Yarn Berry monorepo package; metadata signals (no description, no keywords, cpojer as maintainer) are expected for this ecosystem package and not indicative of spam. ai

Versions (showing 13 of 13)

Version Deps Published
3.2.1 3 / 3
3.2.0 3 / 3
3.1.1 3 / 2
3.1.0 3 / 2
3.0.1 3 / 2
3.0.0 3 / 2
2.3.0 2 / 2
2.2.4 2 / 2
2.2.3 2 / 2
2.2.2 2 / 2
2.2.1 2 / 2
2.2.0 2 / 2
2.1.0 2 / 2

v3.2.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.2.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

2 findings
HIGH Publisher changed: arcanis → yarnbot (on 2023-10-22) provenance

This version was published by a different npm account than previous versions on 2023-10-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

3 findings
HIGH Low-value / spam package indicators (4 signals, score 7) bogus-package

Matched 4 signal(s), weighted score 7: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: sebmck, cpojer. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_DESC_MATCHES_NAME] Description is empty or just restates the package name. • [S_NO_KEYWORDS] No keywords declared.

HIGH Unclaimed maintainer email domain: rome.tools email-domain

Maintainer email '[email protected]' uses domain 'rome.tools' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.4

3 findings
HIGH New obfuscated file: lib/libzipAsync.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: lib/libzipSync.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.