emmet
Emmet — the essential toolkit for web-developers
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:lib/utils/math.js | AI (source-diff): Vendored js-expression-eval math parser; UMD wrapper + new Function() for expression compilation is standard, not malicious network+exec. | ai | |
| typosquat | typosquat.levenshtein:helmet | AI (typosquat): Emmet is a well-established brand predating helmet's popularity; the Levenshtein proximity is coincidental, not impersonation. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require iterates over a hardcoded array ['css']; the path is effectively static and not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:requirejs | AI (phantom-deps): requirejs is a declared runtime dependency used in AMD build/config files; phantom-dep flag is a false positive for this AMD-based package. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): Used to load user-defined JS configuration/snippet files in emmet.js — expected behavior for a developer toolkit supporting JS-based config, with try/catch error handling. | ai | |
| npm-metadata | url-dep:lodash | AI (npm-metadata): Points to the emmetio org's own lodash fork on GitHub — consistent with the package's long history and not an external supply-chain risk. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in evaluateMath.js to evaluate user-selected math expressions in the editor — a legitimate and documented use case for this developer toolkit. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 2.4.11 | 2 / 8 | |
| 2.4.10 | 2 / 8 | |
| 2.4.9 | 2 / 8 | |
| 2.4.8 | 2 / 8 | |
| 2.4.7 | 2 / 10 | |
| 2.4.6 | 2 / 10 | |
| 2.4.5 | 2 / 10 | |
| 2.4.4 | 2 / 10 | |
| 2.4.3 | 2 / 10 | |
| 2.4.2 | 2 / 9 | |
| 2.4.1 | 2 / 9 | |
| 2.4.0 | 2 / 9 | |
| 2.3.6 | 2 / 10 | |
| 2.3.5 | 2 / 10 | |
| 2.3.4 | 2 / 10 | |
| 2.3.3 | 2 / 10 | |
| 2.3.2 | 2 / 10 | |
| 2.3.1 | 2 / 10 | |
| 2.3.0 | 2 / 10 | |
| 2.2.1 | 2 / 10 | |
| 2.2.0 | 2 / 10 | |
| 2.1.6 | 2 / 10 | |
| 2.1.5 | 2 / 10 | |
| 2.1.4 | 2 / 10 | |
| 2.1.2 | 2 / 10 | |
| 2.1.1 | 2 / 10 | |
| 2.1.0 | 2 / 10 | |
| 2.0.2 | 2 / 10 | |
| 2.0.1 | 2 / 10 | |
| 2.0.0 | 2 / 10 | |
| 1.6.3 | 1 / 8 | |
| 1.6.2 | 1 / 8 | |
| 1.6.1 | 1 / 8 | |
| 1.6.0 | 1 / 8 | |
| 1.5.0 | 1 / 8 | |
| 1.4.1 | 1 / 8 | |
| 1.4.0 | 1 / 8 | |
| 1.3.2 | 0 / 8 | |
| 1.3.1 | 0 / 8 | |
| 1.3.0 | 0 / 8 | |
| 1.2.4 | 0 / 8 | |
| 1.2.3 | 0 / 8 | |
| 1.2.2 | 0 / 8 | |
| 1.2.1 | 0 / 8 | |
| 1.2.0 | 0 / 8 | |
| 1.1.7 | 2 / 4 | |
| 1.1.6 | 2 / 4 | |
| 1.1.5 | 2 / 4 | |
| 1.1.4 | 2 / 4 | |
| 1.1.3 | 2 / 4 | |
| 1.1.2 | 2 / 4 |
v2.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.