@emmetio/expand-abbreviation

Reference implementation of Emmet abbreviation expander

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

emmetio-userserge.che

Keywords

emmetabbreviationexpand

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): serge.che is Sergey Chikuyonok, the original Emmet author (matches package.json author email). Transition from emmetio org account to personal account is legitimate for this well-known project.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher serge.che is the original Emmet author; change from emmetio to serge.che is a legitimate account consolidation, not a hijack.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers emmetio-user and serge.che are the same individual (Sergey Chikuyonok) under different account names; not a third-party takeover.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of emmetio org account in favor of personal accounts is consistent with legitimate project administration by the original author.	ai	2026/04/24

Versions (showing 22 of 22)

Version	Deps	Published
0.7.3	12 / 4	2018-12-03
0.7.1	12 / 4	2018-06-06
0.7.0	12 / 4	2018-03-28
0.6.0	12 / 4	2018-03-20
0.5.10	12 / 5	2018-02-19
0.5.9	12 / 5	2018-01-11
0.5.8	12 / 5	2017-06-17
0.5.7	13 / 5	2017-05-28
0.5.6	13 / 5	2017-05-16
0.5.5	13 / 5	2017-05-15
0.5.4	12 / 5	2017-05-14
0.5.3	16 / 5	2017-05-14
0.5.2	16 / 5	2017-05-13
0.5.1	16 / 5	2017-05-10
0.5.0	12 / 5	2017-03-23
0.4.2	12 / 5	2017-03-01
0.4.1	12 / 5	2017-02-21
0.4.0	12 / 5	2017-02-09
0.3.0	12 / 5	2017-02-01
0.2.0	12 / 5	2017-01-31
0.1.1	8 / 5	2017-01-12
0.1.0	8 / 5	2017-01-11

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.1

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (emmetio) were replaced by new maintainers (emmetio-user, serge.che). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: emmetio → serge.che (on 2018-06-06) provenance

This version was published by a different npm account than previous versions on 2018-06-06. 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.

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.10

1 finding

LOW No provenance attestation provenance

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

v0.5.9

1 finding

LOW No provenance attestation provenance

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

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

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