@emmetio/snippets
Emmet snippets
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): serge.che is Sergey Chikuyonok, the original Emmet author (listed in package.json author field). Transition to personal account is legitimate; no hijack indicators. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher serge.che matches the package author field (Sergey Chikuyonok). Legitimate author transition from org account to personal account in 2018. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers emmetio-user and serge.che are the original author's accounts. Legitimate organizational restructuring. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of emmetio account is part of the same legitimate author-driven account reorganization. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.2.12 | 0 / 3 | |
| 0.2.11 | 0 / 3 | |
| 0.2.10 | 0 / 3 | |
| 0.2.9 | 0 / 3 | |
| 0.2.8 | 0 / 3 | |
| 0.2.6 | 0 / 3 | |
| 0.2.5 | 0 / 3 | |
| 0.2.4 | 0 / 3 | |
| 0.2.3 | 0 / 3 | |
| 0.2.2 | 0 / 3 | |
| 0.2.1 | 0 / 3 | |
| 0.2.0 | 0 / 3 | |
| 0.1.2 | 0 / 3 | |
| 0.1.1 | 0 / 3 | |
| 0.1.0 | 0 / 3 |
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
3 findingsAll 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.
This version was published by a different npm account than previous versions on 2018-07-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.