@types/ejs MIT 26 versions

@types/ejs

npm Repository Homepage

TypeScript definitions for ejs

26

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:qs	AI (typosquat): @types/ejs is the canonical DefinitelyTyped package for ejs, not a typosquat of qs.	ai	2026/04/24
typosquat	typosquat.levenshtein:rxjs	AI (typosquat): @types/ejs is the canonical DefinitelyTyped package for ejs, not a typosquat of rxjs.	ai	2026/04/24
typosquat	typosquat.levenshtein:ajv	AI (typosquat): @types/ejs is the canonical DefinitelyTyped package for ejs, not a typosquat of ajv.	ai	2026/04/24
email-domain	unclaimed-email:https://github.com/benliddicott/definitelytyped	AI (email-domain): Author field contains a GitHub URL, not an email. Analyzer misparses the URL as a domain name.	ai	2026/04/24

Versions (showing 26 of 26)

Version	Deps	Published
3.1.5	0 / 0	2023-11-07
3.1.4	0 / 0	2023-10-18
3.1.3	0 / 0	2023-09-23
3.1.2	0 / 0	2023-02-14
3.1.1	0 / 0	2022-05-12
3.1.0	0 / 0	2021-08-17
3.0.7	0 / 0	2021-07-06
3.0.6	0 / 0	2021-02-15
3.0.5	0 / 0	2020-10-20
3.0.4	0 / 0	2020-05-15
3.0.3	0 / 0	2020-04-27
3.0.2	0 / 0	2020-04-02
3.0.1	0 / 0	2020-02-19
3.0.0	0 / 0	2019-12-05
2.7.0	0 / 0	2019-11-27
2.6.3	0 / 0	2019-02-23
2.6.2	0 / 0	2019-02-13
2.6.1	0 / 0	2018-12-03
2.6.0	0 / 0	2018-06-04
2.5.1	0 / 0	2018-04-09
2.5.0	0 / 0	2017-12-11
2.3.33	0 / 0	2016-11-01
2.3.32	0 / 0	2016-10-14
2.3.31	0 / 0	2016-10-05
2.3.30	0 / 0	2016-09-19
2.3.29	0 / 0	2016-07-14

v3.1.4

1 finding

LOW No provenance attestation provenance

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

v3.1.3

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.7

1 finding

LOW No provenance attestation provenance

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

v3.0.6

1 finding

LOW No provenance attestation provenance

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

v3.0.5

1 finding

LOW No provenance attestation provenance

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

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.7.0

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

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

1 finding

LOW No provenance attestation provenance

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

v2.3.32

1 finding

LOW No provenance attestation provenance

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

v2.3.31

1 finding

LOW No provenance attestation provenance

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

v2.3.30

1 finding

LOW No provenance attestation provenance

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

v2.3.29

2 findings

HIGH Unclaimed maintainer email domain: https://github.com/benliddicott/definitelytyped email-domain

Maintainer email 'https://github.com/benliddicott/DefinitelyTyped' uses domain 'https://github.com/benliddicott/definitelytyped' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.