vscode-emmet-helper — Greenflagged

Helper to use emmet modules in Visual Studio Code

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

aeschlioctreframya-rao-araymondzhao

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:out/data.js	AI (source-diff): out/data.js is a minified CSS property data dictionary, expected for an Emmet helper library. Long lines are dense data serialization, not obfuscation or malicious code.	ai	2026/04/24
source-diff	obfuscated-file:lib/cjs/data.js	AI (source-diff): File contains minified CSS/HTML property name arrays for Emmet completion data — not obfuscated malicious code. Long lines are large string arrays, stable for this package.	ai	2026/04/24
source-diff	obfuscated-file:lib/esm/data.js	AI (source-diff): ESM variant of the same Emmet completion data file — minified CSS/HTML property arrays, not obfuscated malicious code. Stable for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Legitimate Microsoft internal maintainer transition; raymondzhao is a known VS Code team member with 187 approved packages and the repo remains under the Microsoft GitHub org.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): aeschli, octref, and raymondzhao are all recognized Microsoft/VS Code ecosystem contributors; this is a legitimate team maintainer setup.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Well-established Microsoft utility package with 152 versions and 49k weekly downloads; sparse README and missing keywords are cosmetic, not indicative of spam or malice.	ai	2026/04/24

Versions (showing 51 of 143)

View all versions

Version	Deps	Published
2.6.4	6 / 6	2021-05-25
2.6.3	6 / 6	2021-05-25
2.6.2	6 / 6	2021-04-06
2.6.1	6 / 6	2021-04-06
2.6.0	6 / 6	2021-04-06
2.5.0	6 / 5	2021-04-02
2.4.4	6 / 5	2021-04-01
2.4.3	6 / 5	2021-03-30
2.4.2	6 / 5	2021-03-22
2.4.1	6 / 5	2021-03-08
2.4.0	6 / 5	2021-03-03
2.3.4	6 / 5	2021-03-02
2.3.3	6 / 5	2021-03-02
2.3.2	6 / 5	2021-02-22
2.3.1	6 / 5	2021-02-18
2.3.0	6 / 5	2021-02-12
2.2.4	6 / 5	2021-02-05
2.2.3	6 / 5	2021-01-04
2.2.2	6 / 5	2020-12-30
2.2.1	6 / 5	2020-12-30
2.2.0	6 / 5	2020-12-30
2.1.2	6 / 5	2020-11-11
2.1.1	5 / 5	2020-10-23
2.1.0	5 / 5	2020-10-21
2.0.9	6 / 5	2020-11-09
2.0.8	5 / 5	2020-10-28
2.0.7	5 / 7	2020-10-19
2.0.6	5 / 5	2020-10-19
2.0.5	4 / 5	2020-10-16
2.0.4	4 / 5	2020-10-13
2.0.3	4 / 5	2020-10-13
2.0.2	4 / 5	2020-10-13
2.0.0	4 / 5	2020-08-14
1.2.17	3 / 4	2020-01-09
1.2.16	3 / 4	2019-09-26
1.2.15	3 / 4	2019-01-17
1.2.14	3 / 4	2019-01-16
1.2.13	3 / 4	2019-01-16
1.2.12	3 / 4	2018-09-14
1.2.11	3 / 4	2018-07-30
1.2.10	3 / 4	2018-06-08
1.2.9	3 / 4	2018-05-11
1.2.8	3 / 4	2018-05-11
1.2.7	3 / 4	2018-04-23
1.2.6	3 / 4	2018-04-20
1.2.5	3 / 4	2018-04-12
1.2.4	3 / 4	2018-03-27
1.2.3	3 / 4	2018-03-26
1.2.2	3 / 4	2018-03-15
1.2.1	3 / 4	2018-03-09
1.2.0	3 / 4	2018-03-01

v2.6.4

1 finding

LOW No provenance attestation provenance

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

v2.6.3

1 finding

LOW No provenance attestation provenance

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

v2.6.2

1 finding

LOW No provenance attestation provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.4

1 finding

LOW No provenance attestation provenance

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

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.4

1 finding

LOW No provenance attestation provenance

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

v2.3.3

1 finding

LOW No provenance attestation provenance

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

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.4

1 finding

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.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

2 findings

HIGH Publisher changed: aeschli → raymondzhao (on 2020-10-13) provenance

This version was published by a different npm account than previous versions on 2020-10-13. 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.0.0

4 findings

HIGH Publisher changed: octref → aeschli (on 2020-08-14) provenance

This version was published by a different npm account than previous versions on 2020-08-14. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: lib/cjs/data.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/esm/data.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.

v1.2.17

1 finding

LOW No provenance attestation provenance

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

v1.2.16

1 finding

LOW No provenance attestation provenance

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

v1.2.15

1 finding

LOW No provenance attestation provenance

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

v1.2.14

1 finding

LOW No provenance attestation provenance

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

v1.2.13

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ramya-rao-a → octref (on 2019-01-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-16. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.12

1 finding

LOW No provenance attestation provenance

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

v1.2.11

1 finding

LOW No provenance attestation provenance

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

v1.2.10

1 finding

LOW No provenance attestation provenance

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

v1.2.9

1 finding

LOW No provenance attestation provenance

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

v1.2.8

1 finding

LOW No provenance attestation provenance

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

v1.2.7

1 finding

LOW No provenance attestation provenance

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

v1.2.6

1 finding

LOW No provenance attestation provenance

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

v1.2.5

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

2 findings

HIGH New obfuscated file: out/data.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.

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.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.