← Home

@emmetio/abbreviation

npm Repository Homepage

Emmet standalone abbreviation parser

35
Versions
MIT
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

emmetio-userserge.che

Keywords

emmetabbreviation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Established Emmet ecosystem package with trusted long-standing publisher; missing gitHead reflects a publish environment change, not a security concern. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance; trusted publisher with 213 approved packages and no rejections. Lack of attestation is a hygiene note, not a security risk. ai

Versions (showing 35 of 35)

Version Deps Published
2.3.3 1 / 8
2.3.2 1 / 8
2.3.1 1 / 7
2.3.0 1 / 7
2.2.3 1 / 9
2.2.2 1 / 9
2.2.1 1 / 9
2.2.0 1 / 9
2.1.1 1 / 9
2.1.0 1 / 9
2.0.2 1 / 9
2.0.1 1 / 9
2.0.0 1 / 9
0.7.0 3 / 4
0.6.6 3 / 4
0.6.5 3 / 4
0.6.4 3 / 4
0.6.3 3 / 4
0.6.2 3 / 4
0.6.1 3 / 4
0.6.0 3 / 4
0.5.1 2 / 4
0.5.0 1 / 4
0.4.6 0 / 5
0.4.5 0 / 5
0.4.4 0 / 5
0.4.3 0 / 5
0.4.2 0 / 5
0.4.1 0 / 5
0.4.0 0 / 5
0.3.1 0 / 4
0.3.0 0 / 4
0.2.0 0 / 4
0.1.1 0 / 4
0.1.0 0 / 4

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

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: serge.che.

LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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