← Home

jed

npm Repository Homepage

Gettext Style i18n for Modern JavaScript Apps

10
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

slexaxton

Keywords

i18nJedgettextinternationalization

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:jest AI (typosquat): Jed is a 14-year-old i18n library with 184k weekly downloads; the name similarity to jest is purely coincidental and not a typosquat. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Jed is a well-established package predating joi's popularity; no impersonation intent. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Jed predates zod by many years; the edit-distance match is a false positive for this long-standing i18n library. ai

Versions (showing 10 of 10)

Version Deps Published
1.1.1 0 / 3
1.1.0 0 / 3
1.0.2 0 / 3
1.0.1 0 / 3
1.0.0 0 / 3
0.5.5 0 / 3
0.5.4 0 / 3
0.5.2 0 / 3
0.5.1 0 / 3
0.5.0 0 / 3

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.